meteora

Create a DLMM instance with DLMM.create(connection, poolAddress), fetch the active bin, then call initializePositionAndAddLiquidityByStrategy with token amounts and a strategy like StrategyType.SpotBalanced spanning a bin range around the active bin.

DAMM v2 uses position NFTs instead of LP tokens, supports Token-2022 extensions, offers dynamic fee schedulers, and costs 0.022 SOL to create a pool versus roughly 0.15 SOL on v1. DAMM v2 is recommended for new pools while v1 remains supported for stable, weighted, and LST pools.

Use the DynamicBondingCurve SDK's createPool method with a config address, base mint, quote mint, token metadata, and supply. The curve handles trading until the graduation threshold is met, then auto-migrates liquidity to DAMM v1 or v2.

DAMM v2 provides full Token-2022 (Token Extensions) support. DLMM and other Meteora programs have varying compatibility, so verify the specific pool program before integrating tokens using extensions.

Slippage errors occur when the price moves beyond your tolerance between quote and execution. Increase the slippageBps parameter, refetch pool state before quoting, and ensure you pass the correct bin arrays from getBinArrayForSwap for DLMM swaps.

For DLMM, call claimSwapFee with the owner and position public keys, or claimAllSwapFee for multiple positions. For DAMM v2, use cpAmm.claimPositionFee with the pool and position addresses.