Straight answers
FAQ: vesting, LP lock and disclosure
7 questions on what happens after launch: on a Verified Meteora launch 5% of the supply vests to the maker over 30 days from migration (an Open bundle launch has no maker vesting) and 100% of the liquidity is permanently locked. The disclosure badge is green below 15%, orange from 15 to 30% and red above 30%.
Vesting, LP lock and disclosure
What happens when the curve completes?
The coin migrates: its liquidity moves into a Meteora DAMM v2 pool with a 1% fee tier. After migration the coin trades in that pool, outside this app's trade panel. 100% of the liquidity is permanently locked, and on a Verified launch the maker's vested allocation starts unlocking at the same moment. An Open bundle launch has no maker vesting. That is the default Meteora route. On a Raydium launch, 100% of the Raydium CPMM liquidity is locked with Raydium's lock program at graduation. Its Fee Key NFT goes to the KABOOM! treasury, so the platform, not the maker, collects the pool fees on the locked liquidity.
How does maker vesting work?
On a Verified launch on the default Meteora route, 5% of the supply is set aside for the maker and moves into a vesting escrow at migration. It is released in 30 equal steps over 30 days from migration, without a cliff, so before migration the maker cannot sell it. No way to cancel the escrow was found, though that is not proven. The maker's own dev-buy tokens are not locked. The Solana coin page shows the schedule and how much has unlocked. An Open bundle launch has no maker vesting. A Raydium launch has no maker vesting: no share of the supply is set aside for the maker.
Is the liquidity locked?
Yes, at migration 100% of the liquidity is permanently locked: 50% in a platform position and 50% in a maker position. The locked liquidity cannot be withdrawn; whether trading fees on the locked positions can be claimed has not been tested yet. The rule is part of the config of every launch tier, Verified and Open bundle, on the default Meteora route, and the coin page reads the LP status from the chain. On a Raydium launch, 100% of the Raydium CPMM liquidity is locked with Raydium's lock program at graduation. Its Fee Key NFT goes to the KABOOM! treasury, so the platform, not the maker, collects the pool fees on the locked liquidity. When a Robinhood Chain coin graduates, PONS mints its pool position straight to the PONS launch locker, a contract whose verified source has no withdrawal function, so that liquidity is locked permanently.
Can anyone mint more tokens or change the name or image?
Every Solana coin has a supply of 1,000,000,000 tokens with 6 decimals. A Meteora launch, the default route, is configured with the bonding-curve SDK's immutable token-authority option, not one of the options that keep a mint authority. That is the launch config, not a recorded check: the coin page reads the mint authority and the metadata from the chain, so check there for each coin. A Raydium launch has no mint authority and no freeze authority: Raydium's LaunchLab program mints all 1,000,000,000 tokens when the coin is created and leaves both empty, so nobody can mint more tokens or freeze a wallet. The coin page reads both from the chain.
What is the disclosure badge?
The badge answers one question: how much of the supply sat with a few related wallets right after launch. Below 15% is green, 15 to 30% is orange and above 30% is red. It has two layers that are never added up: tokens bundled through this platform, which is certain, and detected clusters, which is an estimate. The bundle layer of the disclosure badge is live; cluster figures are not live yet, so no cluster number is shown. Until a layer has a source, the coin page says so instead of showing a number. A Raydium launch is a standard launch, so it has no bundle wallets: the disclosure panel on its coin page reads the launch transaction from the chain, says that no bundle wallets were declared and shows the maker's dev-buy share.
What are detected clusters, and can they be wrong?
A detected cluster is a group of early buyers whose wallets look linked, for example because the same wallet funded them. It is an indication, never proof, and it is never labelled as the maker. It can be wrong in both directions, so a cluster figure is only shown with the false-positive rate the detector measured in its own blind tests. Detection covers Solana mainnet coins only, and the current detector does not report that rate yet, so no cluster figure is shown today.
Where does the data on KABOOM! come from?
From the chain, every time a page loads. Solana coin pages read the pool, its config, the mint, the metadata and the vesting escrow on every refresh, and build trades and candles from the swap events in the pool's own transactions; a candle opens at the previous close and gaps are never filled in. Robinhood Chain coin pages read the coin from the PONS contracts. There is no separate price database.
Guides
- Bonding curve explainedHow a bonding curve prices a new token, where the SOL goes, what migration to a DAMM v2 pool means and how fees work.
- How to spot a rug pullA 5-point check before you buy a new token: supply held by insiders, maker lock, LP lock, mint and metadata authority, and bundled early buys.
- MethodHow the disclosure badge works, the launch rules per tier and route, and the Meteora trading fee per tier: 2% on Verified, 2.5% on Open bundle.