Skip to main content
Creator fees have two separate phases. Locked-LP Fee Keys are a third mechanism. Before the 2026-08-17 upgrade, the creator scale produced a creator Fee Key. Migrations executed after the upgrade assign that share to the platform.
Fee settings depend on the platform and CPMM config. Verify the on-chain values before signing. This page explains mechanics only and is not financial, legal, tax, or investment advice.

​
Phase 1: bonding-curve creator fees

While your token trades on the bonding curve, the platform can charge a creator-fee component on buys and sells.
  • It accrues in the quote token, usually SOL.
  • The platform sets the rate.
  • You can claim it through the LaunchLab creator-fee claim flow.
  • Graduation stops new bonding-curve accrual. Any existing balance remains claimable.

​
Phase 2: CPMM creator fees

Every newly initialized launch graduates to CPMM. CPMM creator fees accrue only when the selected AmmConfig has a non-zero creator-fee rate. By default, the launch creator becomes the CPMM pool creator. A platform can instead set platform_cp_creator, in which case that address receives the CPMM creator-fee rights. The recorded CPMM creator can claim directly. Another payer can also trigger permissionless collection, but CPMM fixes the destinations to the creator’s canonical token accounts.

​
What happens to LP tokens

The platform config stores platformScale, creatorScale, and burnScale. Before the 2026-08-17 upgrade, creatorScale created a creator-owned Fee Key. For migrations executed after the upgrade, LaunchLab combines it with platformScale:
If the locked share is non-zero, one Fee Key NFT goes to the platform’s configured NFT wallet. This NFT controls LP-fee harvesting. It does not control CPMM creator-fee collection. Creator Fee Keys from migrations completed before the upgrade remain with their existing holders.

​
Fee flow summary

​
Before you launch

  • Check the bonding-curve creator_fee_rate.
  • Check whether platform_cp_creator replaces you as the CPMM creator-of-record.
  • For migrations executed after the upgrade, do not treat creatorScale as a promised creator Fee Key allocation. For earlier migrations, verify the existing Fee Key record.
  • Check the CPMM config’s creator-fee rate and fee-on setting.

​
Pointers