Monitoring token migration
Understanding automatic migration from bonding curve to Raydium AMM
Migration happens automatically when the bonding curve fundraising goal is reached. No SDK method needs to be called—the on-chain program handles the transition.
How migration works
When totalFundRaisingB worth of quote tokens have been raised:
Status change — pool status changes from
0(Trading) to1(Migrate)Trading stops — buy and sell transactions are rejected
Liquidity transfer — tokens and quote tokens move from bonding curve vaults to a new AMM pool
LP distribution — LP tokens are distributed according to
migrateCpLockNftScale:burnScale→ burned permanently (liquidity locked forever)creatorScale→ locked via Burn & Earn, creator receives Fee Key NFTplatformScale→ locked via Burn & Earn, platform receives Fee Key NFT
Status complete — pool status changes to
2(Migrated)AMM trading — token now trades on Raydium AMM (CPMM or AMMv4)
Migration destinations
migrateType
Destination
Fee sharing
Notes
'cpmm'
CPMM
Yes
Creator and platform receive Fee Key NFTs for ongoing LP fees
'amm'
AMM v4 (Hybrid AMM)
No
LP tokens burned, no ongoing fee distribution
What happens to fees
Pre-migration (bonding curve)
Fees accumulate in protocol, platform, and creator vaults. These can be claimed anytime using respective claim methods.
Post-migration (AMM pool)
Locked LP tokens earn trading fees from the AMM pool. Fee Key NFT holders claim their share using harvestLockLiquidity(). Fees are proportional to the LP share (creatorScale / platformScale).
Detecting migration
Monitor pool status to detect when migration occurs:
After migration
Once migrated:
Trading continues on the Raydium AMM pool (not the bonding curve)
Bonding curve fees can still be claimed from the launchpad vaults
LP fees are claimed separately using
harvestLockLiquidity()Vesting begins if
cliffPeriodandunlockPeriodwere configured
Last updated
Was this helpful?