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.

A Platform in LaunchLab is a third-party launch environment built on top of Raydium’s LaunchLab program. Platforms can brand themselves, charge their own fees, and configure the post-bonding-curve migration parameters for every token launched under them — without running a separate on-chain program. Raydium’s own launch UI is just one platform among many.

​
Why platforms exist

Raydium wanted LaunchLab to be a shared primitive, not a single branded product. The Platform PDA system lets ecosystems, tooling providers, communities, and meme teams offer curated or branded launch experiences that all settle into the same underlying LaunchLab bonding-curve program and the same CPMM (or AMM v4) post-migration pool. Examples of platforms you might see in the wild:
  • Raydium’s own LaunchLab UI at raydium.io/launchlab — the reference implementation.
  • Partner launchpads — third parties who’ve registered their own Platform PDA to brand the launch experience.
  • Niche platforms — e.g. a community-specific platform that only launches memecoins tied to a particular theme, with a custom fee share funding its treasury.
All of these tokens still live on the same LaunchLab program, graduate to the same CPMM program, and can be routed by the same aggregators.

​
The Platform PDA

Each platform is represented by a Platform PDA stored in the LaunchLab program. Fields include:
FieldDescription
platform_keySeed / identifier for the platform, used to derive the Platform PDA.
platform_fee_destinationAccount that receives the platform’s cut of trading fees pre- and post-migration.
platform_fee_bpsPlatform fee share on pre-migration swaps (varies by platform).
creator_fee_enabledWhether this platform enables post-migration creator-fee sharing via Burn & Earn.
creator_fee_share_bpsIf enabled, share of LP fees that flow to the creator’s Fee Key NFT.
cp_config_idIf post-migration target is CPMM, which AmmConfig to use — chooses fee tier.
name, description, image_urlDisplay metadata used by wallets and UIs that support platform branding.
tokens_launchedCounter or on-chain index of tokens created under this platform.
Exact field names are in the LaunchLab IDL (sdk-api/anchor-idl). The table above is a descriptive overview.

​
What a platform can control

Fee capture:
  • Platform fee share on every pre-migration buy/sell.
  • Post-migration share — when the token graduates, the LP tokens are minted to a multi-party split defined by the platform: a portion to burn (Burn & Earn — a liquidity-locking pattern that lets the locked LP keep claiming its share of pool fees, see user-flows/burn-and-earn), a portion to creator (Fee Key NFT), and a portion to the platform itself.
Post-migration destination:
  • CPMM (default if creator fees enabled) with a AmmConfig chosen via cp_config_id. Different AmmConfigs have different fee tiers; a platform can pick a higher-fee tier if its launches are high-volume speculative assets.
  • AMM v4 (if creator fees disabled) — for backward compatibility with the original LaunchLab flow.
User experience:
  • Branding metadata used by the Raydium app and any wallet / explorer that surfaces LaunchLab tokens.
  • Launch-page customization — platforms that host their own frontend can filter tokens to only show their own platform’s launches.

​
What a platform cannot control

  • Bonding-curve math. The curve shape (logistic, exponential, etc.) is part of the LaunchLab program itself. Platforms choose from the supported curves; they cannot add arbitrary custom curves.
  • Migration threshold logic. The condition that triggers graduation to CPMM / AMM v4 (target market cap reached) is program-enforced.
  • Core security / audit posture. Every platform inherits LaunchLab’s audit history; a malicious platform cannot bypass it by altering the program.

​
Registering a platform

The LaunchLab program exposes a create_platform instruction (exact name from the IDL). Callers pass:
  • The seed that will derive the Platform PDA.
  • The fee destination account.
  • Desired fee bps (subject to program-level caps).
  • Post-migration config (CPMM AmmConfig ID if applicable).
  • Branding metadata.
Rent for the Platform PDA is paid by the creator. Updates to branding and some fee parameters are permitted post-creation by the platform’s authority; structural parameters (migration destination program) typically are not. See products/launchlab/instructions for the exact instruction signature in the current LaunchLab IDL.

​
Economic interaction

A single swap on a LaunchLab bonding curve distributes value roughly like this (exact ratios set by the platform): 
Buyer pays:                  100 SOL
Protocol fee (LaunchLab):    – small %
Platform fee:                – platform_fee_bps%
Creator fee (pre-migration): – creator_fee_bps% (if enabled)
Remainder (to curve):        ~ rest
Post-migration, LP tokens are split per the platform config: 
LP tokens minted at graduation:  100%
  → Burn & Earn (burned):          X%  (default on Raydium: 90)
  → Creator Fee Key NFT:           Y%  (default on Raydium: 10)
  → Platform:                      Z%  (platform-configured; may be 0)
The Burn & Earn share converts to shared fee income distributed to the Fee Key holder — which, under Raydium’s own defaults, is the burn “vault” representing broad-market fee backing for token trust.

​
Integrator notes

  • Listing tokens by platform. Use the API pool-info / mint endpoints with a platform filter (when supported) to list only tokens launched under a specific Platform PDA.
  • Branding display. If you build a wallet or explorer that surfaces LaunchLab tokens, reading the platform’s name / image URL from the Platform PDA is far better UX than showing “LaunchLab” for every token.
  • Fee math. Every bonding-curve quote must account for the platform fee in addition to the protocol and creator fees. The SDK’s quote helpers do this automatically when the platform PDA is supplied.

​
Where to go next

Sources:
  • LaunchLab program IDL bundled in the Raydium SDK v2: raydium-io/raydium-sdk-V2 under src/raydium/launchpad/.
  • api-v3.raydium.io/launchlab/platforms endpoints (when available).