Meme Token Creator Fees: What to Verify
Creator fees are often summarized as one percentage, but LaunchLab separates the funding phase from the post-migration pool phase. The payer, fee asset, accounting account, claim instruction, and party entitled to claim can change at graduation. A technically accurate review therefore identifies each fee stream and reads the configuration for the exact platform and pool rather than applying a global assumption.
Editorial research by Coinatio, checked against the primary documentation cited below. Educational content only.
- Pre-migration creator fees accrue from bonding-curve trades and are distinct from CPMM creator fees after graduation.
- Post-migration rights can be represented by a transferable Fee Key, so the current holder matters more than the original recipient.
- Platform configuration and CPMM AmmConfig determine actual rates and splits for a specific launch.
- Fee accrual is variable and claimable balances can be reduced by transfer fees, prior claims, and transaction costs.
Pre-migration fee accounting
While a token trades on the bonding curve, buy and sell instructions apply the fee settings linked to the launch and its platform. The creator component is generally denominated in the quote token, commonly SOL represented through wrapped SOL mechanics at the token-account layer. It accumulates through LaunchLab accounting and can be claimed with the protocol's creator-fee instruction. Protocol, platform, migration, and creator amounts should not be collapsed into one number because they have different destinations and authorities.
To verify the stream, decode PoolState and its PlatformConfig, then inspect the fee vault and relevant counters. Confirm the creator address stored in PoolState and the authority required by the claim instruction. A displayed lifetime total is not the same as a currently claimable balance because previous claims may already have transferred assets. Quote-vault balance alone is also insufficient because it combines real curve quote with pending fee components.
Post-migration fees and Fee Keys
At migration, LaunchLab can create a CPMM pool and divide the LP position according to PlatformConfig. Raydium documents a default for its own LaunchLab experience in which a large portion is placed into Burn & Earn and a creator portion is represented by a Fee Key NFT. Other platforms can select different creator, platform, and locked shares within protocol rules. Read the exact platform account used by the launch rather than copying Raydium's reference split.
Burn & Earn locks the underlying LP position so its liquidity cannot be withdrawn, while a Fee Key represents authority to collect fees associated with the locked position. The Fee Key is transferable. If the original creator sends or sells it, the new holder receives the claim right and the creator no longer controls that stream. Verification must therefore inspect current token ownership of the Fee Key and map its metadata or lock account back to the correct LP position and CPMM pool.
How CPMM charges and records fees
Raydium CPMM has a trade fee configured through AmmConfig and may have an independent creator fee. The creator fee is not necessarily a percentage of the trade fee. Depending on creator_fee_on and swap direction, it can be taken from the input or output side. Protocol and fund portions are derived from the trade fee, while creator amounts occupy their own accrued counters. These distinctions affect both user quotes and reconciliation.
For a reproducible calculation, fetch AmmConfig, PoolState, mint extensions, and swap direction. Apply Token-2022 transfer fees before or after pool fees at the stage specified by the token program and CPMM math. Use native integer units and documented rounding. To reconcile claims, compare accrued creator counters, claim instructions, destination token accounts, and post-transaction balances. A fee estimate based only on reported volume and one headline rate can be wrong when direction, fee side, or transfer-fee extensions vary.
- Separate curve-phase and pool-phase fee records.
- Read PlatformConfig and AmmConfig live for the exact launch.
- Resolve current Fee Key ownership before naming a beneficiary.
- Account for Token-2022 transfer fees and already claimed amounts.
Limitations and responsible reporting
Fee parameters can differ across platforms and can be represented differently by APIs. Some interfaces report gross accrual, others report unclaimed balances, and some combine token0 and token1 using an external price. Keep amounts in their native assets unless the conversion source and timestamp are explicit. A Fee Key can also be lost, transferred to a contract, or held by a multisig, complicating attribution.
Creator fees describe protocol cash flows, not a fixed income schedule. They depend on actual eligible trades, fee configuration, asset transfer rules, and successful claims. Avoid extrapolating a short observation window or presenting a fee right as a predictable return. The defensible output is a map of mechanisms, current authorities, balances, and transaction evidence at a stated slot.
Sources
This article explains technical and market-data concepts. It is not financial, legal, tax, or investment advice. Verify current chain state and primary documentation independently.
