Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.raydium.io/llms.txt

Use this file to discover all available pages before exploring further.

Two separate mechanisms. Creator fees have a pre-migration phase (fees accrue while the token is still on the bonding curve) and a post-migration phase (fees accrue after graduation to the CPMM/AMM v4 pool). They’re funded differently and claimed differently. This page covers both.

​
Pre-migration: direct fee accrual

While a token is still on the bonding curve, every buy and every sell pays a creator-fee component that accumulates in a per-token vault. The creator (the wallet that launched the token) can claim from the vault at any time. Characteristics:
  • Denominated in the quote token (usually SOL).
  • Configured by the platform (platform config controls whether creator fees are on and at what bps).
  • Claimable anytime from the Portfolio page on the LaunchLab UI; programmatically via the LaunchLab claim_creator_fees instruction (exact name in the IDL).
  • Continues until graduation; at graduation, residual pre-migration fees are claimable but no new pre-migration fees will accrue.

​
Post-migration: Fee Key NFT via Burn & Earn

When a token’s bonding curve reaches its target and liquidity migrates to a CPMM (or AMM v4) pool, LP tokens are minted and split according to the platform’s configuration. The split always sums to 100% and always involves some combination of:
  • Burned — transferred into Burn & Earn for permanent locking. The Fee Key for this portion is held by a platform-controlled or burn-designated account.
  • Creator — a Fee Key NFT minted directly to the token creator’s wallet. This Fee Key represents the right to collect LP trading fees from the creator’s share of LP tokens.
  • Platform — optional; a share that flows to the platform treasury as another Fee Key NFT.

​
Raydium’s own LaunchLab defaults

ShareDefault on raydium.io/launchlab
Burned (Burn & Earn, perpetually locked)90%
Creator (Fee Key NFT)10%
Platform0% (Raydium’s platform does not take a platform LP share)
At these defaults, only the creator claims trading fees from their share; the other 90% is locked and its fees go to Burn & Earn (flowing back to the trust-signalling mechanic rather than any individual pocket).

​
Other platforms

Third-party platforms building on LaunchLab can configure their own split. A platform that wants to fund itself via post-migration LP fees can set (say) 70 / 10 / 20 (burn / creator / platform). See products/launchlab/platforms for the Platform PDA fields that drive this. Regardless of split, the mechanism is the same: each non-burned share is represented as a Fee Key NFT, which can be traded, transferred, or collected against.

​
What happens if post-migration creator fees are disabled

If a platform sets creator_fee_enabled = false, the graduated token does not go through Burn & Earn. Instead, it migrates to an AMM v4 pool using the legacy LaunchLab migration path. In that mode, the creator does not receive a Fee Key NFT, and there is no program-level post-migration creator fee. Some creators in this mode use an off-chain CLI tool to claim optional post-migration fees configured via creatorFeeOn — see products/launchlab/instructions for the on-chain surface.

​
The 0.1% token-share referral

Separately from LP-fee sharing, LaunchLab creators (and any user, really) can share a token page link with their wallet as the referrer. When anyone trades that token (or other LaunchLab tokens in the same session) via the shared link:
  • 0.1% of every trade is airdropped to the referrer’s wallet.
  • Paid in SOL or the pool’s quote token.
  • Paid automatically on every trade; no claim step.
This is a distinct product from the 1% swap referral covered in user-flows/referrals-and-blinks. The 1% referral applies to Raydium’s spot swap UI; the 0.1% token share referral applies to LaunchLab token pages specifically.

​
Claiming fees

​
Creator vault (pre-migration)

import { Raydium, TxVersion } from "@raydium-io/raydium-sdk-v2";
const raydium = await Raydium.load({ owner, connection });
const { execute } = await raydium.launchlab.claimCreatorFees({
  mint,           // launched token mint
  txVersion: TxVersion.V0,
});
await execute({ sendAndConfirm: true });

​
Fee Key NFT (post-migration)

Holding the Fee Key in your wallet is enough — claim from the Portfolio page, or programmatically via the relevant pool program’s fee-claim instruction. See products/cpmm/instructions or the AMM v4 equivalent for the on-chain surface.

​
Integrator checklist

  • Show both fee streams. A creator-dashboard that only shows one of “pre-migration vault” / “post-migration Fee Key” leaves money on the table for users who don’t know the other exists.
  • Respect Fee Key ownership transfers. If a creator sells or transfers their Fee Key NFT, the previous owner loses access to future fee claims. Your UI should read the current NFT holder each time, not cache the original creator address.
  • Platform-config drift. Raydium’s defaults may change. For any platform other than Raydium’s own, always read the Platform PDA live to see the actual burn / creator / platform split for that specific launch.
  • Token-2022 collateral and fee tokens. Creator fees can be denominated in Token-2022 tokens with transfer fees; factor the transfer-fee haircut into any displayed “claimable fee” number.

​
Where to go next

Sources:
  • LaunchLab program IDL and claim_creator_fees instruction.
  • Raydium LaunchLab UI defaults as observed on raydium.io/launchlab (2026-04).