lez-programs/programs/amm/src/lib.rs

//! The AMM Program implementation.

pub use amm_core as core;

pub mod add;
pub mod initialize;
pub mod new_definition;
pub mod remove;
pub mod swap;
pub mod sync;

mod tests;
chore: initial repository setup for programs 2026-03-17 18:08:53 +01:00			`//! The AMM Program implementation.`

			`pub use amm_core as core;`

			`pub mod add;`
feat(amm): add Initialize instruction with config-gated chained calls Introduce a singleton AMM configuration account, a PDA derived from the constant "CONFIG" seed, created once via a new `Initialize` instruction. The config stores the Token Program ID the AMM issues every chained call to, replacing the previous behavior of trusting the program owner of a caller-supplied holding. The config account's existence is the Program's initialization gate: the chained-call instructions (new_definition, add_liquidity, remove_liquidity, swap_exact_input, swap_exact_output) now take the config as their first account, validate it against `compute_config_pda(self_program_id)`, and read the Token Program ID from it on demand — rejecting calls until the Program is initialized. Vaults and user holdings are asserted to match the configured Token Program. sync_reserves is left ungated, as it cannot act on a pool that could not have existed before initialization. - amm_core: AmmConfig type, compute_config_pda/_seed, Initialize variant - amm: initialize.rs + config threading through chained-call instructions - guest: initialize instruction; config + self_program_id on gated calls - tests: config fixtures, init-gate unit tests, end-to-end Initialize VM test 2026-06-17 16:29:30 +02:00			`pub mod initialize;`
chore: initial repository setup for programs 2026-03-17 18:08:53 +01:00			`pub mod new_definition;`
			`pub mod remove;`
			`pub mod swap;`
feat(amm): add SyncReserves instruction Adds a new `SyncReserves` instruction that updates a pool's recorded reserves to match the actual vault balances. This allows the pool to absorb donations (direct token transfers to vaults) without breaking the invariant — only upward adjustments are permitted; vaults may not be under-collateralized relative to reserves. Vault reading helpers (`read_fungible_holding`, `read_vault_fungible_balances`) are implemented in `amm_core` so they can be shared across instructions without crossing crate boundaries. 2026-04-08 10:57:47 -03:00			`pub mod sync;`
chore: initial repository setup for programs 2026-03-17 18:08:53 +01:00
			`mod tests;`