Skip to main content
This page pairs with products/clmm/accounts (what the accounts are) and products/clmm/math (what the math is). It is authoritative for arguments and account ordering; specific byte layouts come from the IDL.

Instruction inventory

Most admin-only instructions (CreateAmmConfig, UpdateAmmConfig, UpdatePoolStatus, CreateSupportMintAssociated, CreateOperationAccount, UpdateOperationAccount, CloseProtocolPosition) are gated by the program’s hardcoded admin pubkey. CreatePermissionPda / ClosePermissionPda accept either the admin pubkey or a dedicated permission_pda_admin key. Reward-stream admin instructions (TransferRewardOwner, CollectRemainingRewards) are gated by the reward funder, not the program admin. V2 suffix means “supports Token-2022 on vaults / NFT, requires bitmap-extension slot”. The SDK picks V2 by default for new pools.

CreatePool

Arguments
Accounts (abridged) Preconditions
  • token_mint_0 < token_mint_1 by byte order.
  • amm_config.disable_create_pool == false.
  • Mints are not rejected by the Token-2022 extension allow-list.
Postconditions
  • pool_state.sqrt_price_x64 = sqrt_price_x64, tick_current = floor(log_{1.0001}(price)).
  • pool_state.liquidity = 0 (no positions yet).
  • pool_state.fee_on = FromInput (legacy default).
  • pool_state.dynamic_fee_info is zeroed (dynamic fee disabled).

CreateCustomizablePool

Recommended for new pools. Same effect as CreatePool plus per-pool fee-collection mode and an optional dynamic-fee opt-in. Arguments
Accounts (abridged) — same as CreatePool plus, when enable_dynamic_fee = true: Preconditions — same as CreatePool. If enable_dynamic_fee = false, dynamic_fee_config is ignored. Postconditions
  • pool_state.fee_on set to the chosen CollectFeeOn variant.
  • If dynamic fee was enabled: pool_state.dynamic_fee_info is initialized from the supplied DynamicFeeConfig (five calibration parameters copied; state fields zeroed).
  • Otherwise: pool_state.dynamic_fee_info is zeroed (= dynamic fee inactive forever for this pool).
fee_on and the dynamic-fee enablement bit are set only at pool creation. There is no in-place upgrade — pools created via legacy CreatePool cannot retroactively gain dynamic fee or single-sided fee. New deployments should default to this instruction.

CreatePermissionedPool

Both CreatePool and CreateCustomizablePool derive the pool PDA from ["pool", amm_config, token_mint_0, token_mint_1], so there is exactly one canonical pool address per (config, mint0, mint1) triple — a second init at the same seeds fails. CreatePermissionedPool lifts that restriction by folding a client-supplied seed_index: u16 into the pool PDA seeds, allowing multiple pools for the same pair and fee tier — each at its own address. Because an arbitrary pool address is a privileged capability, the payer must hold a Permission PDA that authorizes it. Everything else about the pool is identical to CreateCustomizablePool: it takes the same CreateCustomizableParams and supports single-sided fee and the dynamic-fee opt-in. Arguments
Accounts (abridged) — same as CreateCustomizablePool plus, at the front: The pool_state PDA is derived from ["pool", amm_config, token_mint_0, token_mint_1, seed_index.to_le_bytes()]. Preconditions
  • seed_index != 0. A seed_index of 0 is reserved for legacy pools and is rejected here; the [0, 0] seed component is what makes a legacy pool address collapse to the classic four-seed form.
  • The permission PDA for payer exists (created by an admin via CreatePermissionPda).
  • Same mint / allow-list rules as CreatePool.
Postconditions
  • A new pool_state exists at the seed_index-derived address, with pool_state.seed_index = seed_index.
  • All other post-state matches CreateCustomizablePool (fee mode, optional dynamic fee).
This instruction does not widen general pool-creation access — permissionless creation continues through CreatePool / CreateCustomizablePool, which remain one-pool-per-pair. CreatePermissionedPool exists for the specific case where a whitelisted operator needs several pools for the same pair (e.g. differing initial prices or launch cohorts) and holds a Permission PDA granted by the admin.

OpenPositionV2 / OpenPositionWithToken22Nft

Create a new position inside an existing pool. Arguments
Accounts (abridged) Math — see products/clmm/math. Given base_flag, the program resolves either liquidity or (amount_0_max, amount_1_max) into the actual L and the actual token amounts consumed. Preconditions
  • tick_lower < tick_upper, both multiples of pool.tick_spacing, within [MIN_TICK, MAX_TICK].
  • Required tick arrays passed and initialized (or created here via InitTickArray CPI in the transaction).
  • User has at least amount_0_max and amount_1_max in the source ATAs.
Postconditions
  • personal_position exists, liquidity set, fee_growth_inside_last snapshotted.
  • Tick-array entries at tick_lower and tick_upper updated (liquidity_gross += L, liquidity_net ± L, fee-growth snapshots maintained).
  • pool_state.liquidity += L if position is in range (tick_lower ≤ tick_current < tick_upper).
  • The position NFT mint records pool_state as freeze authority. Mint authority is removed after the single NFT is minted. Recording the freeze authority does not change the NFT token account’s state.
  • The NFT token account remains unfrozen unless the instruction is OpenPositionV2 or OpenPositionWithToken22Nft and either vault mint’s freeze authority matches CLMM’s restricted-issuer list. Only that matching V2 path freezes the account. OpenPosition V1 does not freeze.
Common errorsInvalidTickIndex, NotApproved, ZeroAmountSpecified, TransactionTooLarge (if too many tick arrays).
Position freezing does not add declared instruction accounts or arguments. Clients can open these positions with the existing V2 layouts. The behavior is selected on-chain from vault_0_mint and vault_1_mint.

IncreaseLiquidityV2

Add liquidity to an already-open position. Arguments
Accounts — like OpenPosition minus the NFT mint (position already exists; the NFT is passed as the owner’s ATA holding 1 token). Effect
  • Transfers amount_0_actual / amount_1_actual from user → vaults.
  • Increments personal_position.liquidity and pool_state.liquidity (if in range), and the endpoint-tick liquidity_gross / liquidity_net accordingly.
  • Collects fees and rewards owed since last touch and credits them to tokens_fees_owed_{0,1} / reward_amount_owed. Those are paid out only on DecreaseLiquidity or CollectReward, not on increase.

DecreaseLiquidityV2

Remove liquidity from a position. Arguments
Accounts — same shape as IncreaseLiquidity. Effect
  • Computes (amount_0, amount_1) for the removed L given current sqrt_price_x64.
  • Settles fees/rewards accrued since the last touch, same as IncreaseLiquidity.
  • Transfers amount_0 + fees_owed_0 and amount_1 + fees_owed_1 out of vaults to the user.
  • Decrements liquidity counters; if the new personal_position.liquidity == 0, the position is eligible for ClosePosition.
Slippageamount_0_min and amount_1_min are the minimums the user accepts net of Token-2022 transfer fees on the output side.

ClosePosition

Burn the position NFT and close PersonalPositionState. Declared accounts Remaining accounts
  • Unfrozen NFT: none required; an extra pool account is harmless because the handler does not read it.
  • Frozen NFT: append personal_position.pool_id as the first remaining account. The program loads it as PoolState and uses its PDA seeds to sign the thaw.
Preconditions
  • personal_position.liquidity == 0.
  • tokens_fees_owed_{0,1} == 0.
  • All reward counters reward_amount_owed == 0.
(I.e., collect everything and decrease-to-zero first.) Effect
  • If the NFT token account is frozen, verifies the first remaining account equals personal_position.pool_id, then thaws it with the pool PDA.
  • Burns the NFT.
  • Closes the NFT token account and personal_position, refunding rent to nft_owner. If the position NFT uses Token-2022, it also closes the NFT mint; classic SPL Token mints cannot be closed and remain with supply zero.
The thaw, burn, and close are atomic. The NFT cannot become transferable between those steps. Conditional client break — the declared IDL layout is unchanged, so legacy clients continue to close existing and unfrozen positions. A legacy builder that omits the pool remaining account fails with AccountLack when closing a frozen position. Passing the pool for every close is the simplest compatible strategy.

SwapV2

Walk the liquidity curve; exact input or exact output depending on is_base_input. Arguments
Accounts (abridged) Callers pass a ranked list of tick arrays covering the expected swap walk; the program uses as many as it needs. The SDK computes this list via PoolUtils.computeAmountOutFormat or the API’s quote endpoint. Preconditions
  • pool_state.status allows swap.
  • now >= open_time.
  • sqrt_price_limit_x64 is on the correct side of sqrt_price_x64 for the direction.
Common errorsExceededSlippage, SqrtPriceLimitOverflow, TickArrayNotFound, LiquidityInsufficient. What SwapV2 does internally that callers should know about (post-2025 release):
  1. Dynamic fee surcharge — if pool.dynamic_fee_info is non-zero, the program updates the volatility accumulator using the tick distance traversed since the last swap (with the filter/decay rules from products/clmm/fees) and adds a dynamic_fee_component on top of AmmConfig.trade_fee_rate. Total fee is capped at 10% (MAX_FEE_RATE_NUMERATOR / 1_000_000).
  2. Limit-order matching — when the price walk crosses a tick that holds open limit orders, the program first fills available limit-order liquidity at that tick (FIFO by order_phase), then proceeds along the LP liquidity curve. Filled amounts update tick.unfilled_ratio_x64 and tick.part_filled_orders_remaining for later settlement; orders themselves remain unspent until their owner calls SettleLimitOrder.
  3. Single-sided fee routing — when pool.fee_on = Token0Only or Token1Only, the swap step still computes the same input-output trade; the fee is then routed to the configured side. For directions where the configured fee side is the output, the fee is deducted from the swap output (the user receives out − fee); for directions where it is the input, behavior matches FromInput. See is_fee_on_input(zero_for_one) and is_fee_on_token0(zero_for_one) on PoolState.
Swap (V1) implements the same dynamic fee, single-sided fee routing, and limit-order matching as SwapV2; the only feature it lacks is Token-2022 support — both vaults must be classic SPL Token. Pools with any Token-2022 mint must be swapped via SwapV2. The aggregator and SDK already prefer V2 for every CLMM leg so callers don’t have to branch on mint type.

OpenLimitOrder

Place a sell order at a specific tick. The order sits in a per-tick FIFO cohort and fills as price walks past. Arguments
Accounts (abridged)
Account-list change (2026-07 release). OpenLimitOrder now also takes the output-side accounts — output_token_account, output_vault, and output_vault_mint — in addition to the input side. They are used only for validation: the program rejects the order if the owner’s input or output token account is frozen. This guarantees that a fill can actually be settled to the owner’s output ATA, which matters for allow-list / default-frozen Token-2022 mints (e.g. permissioned tokens) where an account may not yet be thawed. Clients built against the older single-sided account list must add the three output accounts.
Preconditions
  • Neither input_token_account nor output_token_account is frozen (else NotApproved).
  • pool_state.status allows both the swap (bit 4) and limit-order (bit 5) operations (else NotApproved).
  • tick_index % pool.tick_spacing == 0 and within [MIN_TICK, MAX_TICK].
  • tick_index is on the right side of pool.tick_current for the chosen direction (selling token0 → tick must be above current, and vice versa). Selling at a tick already crossed would be matched immediately and is rejected.
Postconditions
  • limit_order exists, snapshotting tick.order_phase and tick.unfilled_ratio_x64 at open time.
  • tick.orders_amount += amount (in the current cohort).
  • limit_order_nonce.order_nonce += 1.
  • OpenLimitOrderEvent emitted.
Common errorsNotApproved (input or output token account frozen, or the pool has swap / limit-order disabled), InvalidLimitOrderAmount (zero or below the pool’s minimum), InvalidTickIndex (out of [MIN_TICK, MAX_TICK], or on the wrong side of tick_current for the chosen direction), TickAndSpacingNotMatch (tick_index % pool.tick_spacing != 0), OrderPhaseSaturated.

IncreaseLimitOrder

Add to an existing open order. Only callable by the order’s owner. Arguments
Accounts — like OpenLimitOrder minus the nonce account; the limit_order PDA is passed directly. Preconditions
  • limit_order.owner == signer.
  • The order is still in the same cohort (tick.order_phase == limit_order.order_phase). If the cohort has already begun filling, the order is partially settled — the caller should call DecreaseLimitOrder or SettleLimitOrder first to roll forward.
Effect
  • Transfers amount from owner ATA to input_vault.
  • limit_order.total_amount += amount; tick.orders_amount += amount.

DecreaseLimitOrder

Reduce or fully cancel an open order. Pays the unfilled remainder back to the owner, plus any output already settled by past partial fills. Arguments
Accounts — both input and output token sides: Effect
  • Recomputes the order’s filled amount from the cohort’s unfilled_ratio_x64 since open.
  • Sends filled output to output_token_account.
  • Sends amount of unfilled input back to input_token_account.
  • Updates limit_order accordingly. If the new unfilled remainder is zero, the program closes the account and refunds rent to owner.

SettleLimitOrder

Push filled output tokens to the owner without changing the order’s unfilled remainder. Useful when auto_withdraw keepers want to drip-pay long-running partial fills. Caller — either the order’s owner, or the program’s limit_order_admin (an off-chain operational hot wallet that runs an automated keeper loop). The keeper has no other authority — it cannot move user funds outside of pushing filled output to the order’s owner ATA. Accounts Effect
  • Computes the cumulative output owed using (limit_order.unfilled_ratio_x64, tick.unfilled_ratio_x64).
  • Transfers the delta to output_token_account.
  • Updates limit_order.settled_output.
  • Does not close the order; it is still open against any remaining input.

CloseLimitOrder

Close a fully-consumed order account. Rent is always returned to limit_order.owner regardless of who signs. Caller — either owner or limit_order_admin. Preconditions
  • The order has zero unfilled remainder (either amount == total_amount was filled and settled, or the owner previously decreased the order to zero and forgot to close).
Effect
  • Closes limit_order; rent is sent to limit_order.owner.

CreateDynamicFeeConfig (admin)

Create a reusable parameter set under a u16 index. Arguments
Accounts Common errorsInvalidDynamicFeeConfigParams if decay_period <= filter_period or any 0-valued field is out of bounds.

UpdateDynamicFeeConfig (admin)

Modify an existing DynamicFeeConfig. Pools that already snapshotted the config at creation time are not retroactively updated; only newly-created pools that reference this config will pick up the new values. Arguments — same five calibration fields as CreateDynamicFeeConfig (filter_period, decay_period, reduction_factor, dynamic_fee_control, max_volatility_accumulator); index is fixed at creation and not re-passed here.

CollectProtocolFee / CollectFundFee

Identical shape to CPMM’s CollectProtocolFee / CollectFundFee. Signer must match AmmConfig.owner / AmmConfig.fund_owner. Sweep accrued protocol/fund fees from the pool’s vaults to a recipient, zero the corresponding PoolState.protocol_fees_* / fund_fees_* fields.

InitializeReward

Add a new reward stream to a pool. Up to 3 streams may be active at once. Arguments
Accounts Preconditions
  • Less than 3 streams currently active on the pool.
  • Funder deposits total_emission = emissions_per_second × (end_time − open_time) worth of reward token into the vault as part of this instruction.
  • Whitelisted reward mint per operation_state.

SetRewardParams

Extend, top up, or change emission rate on an existing reward stream. Typically called by a pool creator or the Raydium multisig. Constraints live on-chain: you can usually extend end_time or increase emissions, not shrink them retroactively. Check operation_state’s owner list.

UpdateRewardInfos

Pure bookkeeping — settles reward_growth_global_x64 to the current time by multiplying emissions_per_second × Δt / liquidity. Called internally by every liquidity-touching instruction. Exposed as a standalone instruction because external actors (UIs, cranks) sometimes want to trigger it.

CollectReward

Position owner claims owed reward tokens. Accounts Effect
  • Settles reward growth (same pattern as fees).
  • Transfers the owed amount to the recipient ATA, zeroes reward_amount_owed[i].

State-change matrix

Where to go next

Sources: