How to Verify a Launchpad Token DEX Migration

Record the Solana cluster, base mint address, expected quote mint, and claimed launchpad. Query the mint account directly and verify that it is owned by the original SPL Token Program or Token-2022 Program. Note supply, decimals, mint authority, freeze authority, and any Token-2022 extensions. Names, symbols, images, and metadata URIs are not unique identifiers and can be copied by another mint.

Obtain the current LaunchLab and Raydium CPMM program IDs from Raydium's official program-address page or live API. Do not copy program IDs from a transaction description supplied by the token creator. On mainnet, the LaunchLab PoolState account must be owned by the canonical LaunchLab program. Decode it with the matching IDL and confirm its base_mint and quote_mint fields match the identifiers already recorded.

Read PoolState status and migrate_type. Funding means curve trading remains active. Migrate means the target was reached but settlement is pending. Migrated means the migration instruction completed. Locate the signature that changed the status and inspect its outer and inner instructions. A CPMM migration should invoke LaunchLab, then create or initialize accounts under the canonical CPMM program through a cross-program invocation.

Confirm that token movements leave the LaunchLab vaults and arrive in destination vaults associated with the same base and quote mints. Check emitted events when available, but do not rely on event text alone. Account owners and mint relationships are stronger evidence. Record the transaction slot, signature, PoolState, destination PoolState, and both vault addresses. If the transaction failed or only simulated, it is not evidence of migration.

Decode the destination CPMM PoolState and verify its program owner, token0 and token1 mints, AmmConfig, LP mint, token vaults, and observation account. CPMM sorts mint keys when deriving its pool PDA, so base token order is not a semantic distinction. Each vault must be a token account for the corresponding mint and must be controlled by the expected program-derived authority. The LP mint should connect to the pool state rather than an unrelated pool with the same pair.

Inspect initial reserve deposits and compare them with the migration transaction. After launch, later swaps and liquidity operations change raw balances, so current reserves need not equal initial deposits. Raw vault balances can also contain accrued protocol, fund, or creator fees excluded from curve balances. If you need the current executable price, use decoded fee counters and CPMM math or simulate a swap rather than dividing raw balances without adjustment.

• Mint account matches the advertised token address.
• Launch PoolState is owned by LaunchLab and reports Migrated.
• Migration signature is successful and invokes the expected DEX program.
• Destination pool and vaults contain exactly the launch base and quote mints.
• LP lock or Fee Key claims are checked separately from pool existence.

Raydium APIs and explorers are useful indexes, but they are secondary views. An API can lag, omit a new pool, or normalize token metadata incorrectly. An explorer may not decode a newly revised instruction. When sources disagree, query account data through a second RPC endpoint, check finalized commitment, and decode against the protocol's current IDL. Automation should fail closed on unknown account layouts or program IDs.

This procedure proves that a specific mint followed a specific migration path into a specific pool. It does not prove the creator controls no other token accounts, that liquidity is permanently locked, or that the pool offers a suitable execution price. Burn & Earn positions, Fee Key ownership, mint extensions, holder concentration, and current reserves require separate checks. Publish the raw identifiers so readers can repeat every step.