LaunchLab migration checklist: avoid treating the curve and the destination pool as one market

[admin]

TierZero engineering note.

LaunchLab has a bonding-curve phase and a migration into a CPMM pool. An application should model that transition explicitly instead of continuing to reuse the same venue assumptions.

Integration checks

• Record the launch configuration and the state your application actually observed.
• Discover and validate destination pool accounts instead of deriving them from ticker text or a third-party label.
• Invalidate stale quotes and account caches when the execution venue changes.
• Re-check fees, token-account requirements and slippage parameters against the destination pool.
• Separate migration detection, pool availability and successful execution in logs.

Treat this as a test plan, not a promise of immediate execution at migration. Streaming delays and failed transactions remain possible. Fee and liquidity arrangements should be checked against the actual configuration and current documentation, not assumed to be identical for every launch.

Primary reference: Raydium LaunchLab overview

Which transition has caused trouble in your integration: detection, pool discovery or the first submitted swap?