The nodes and the fields they write
Each layer in the editor maps to fields of the PlatformConfig, the curve rule or the CPMM config, with the bounds Raydium enforces.
Field map
| Node | On-chain field | Bounds |
|---|---|---|
| Curve | Supply, TotalSellA, TotalFundRaisingB, MigrateRateA | raise ≥ 24 SOL (5 USD1), sell ≥ 20%, migrate ≥ 15% |
| Fees | fee_rate, creator_fee_rate | platform 0 to 5%, creator 0 to 0.5% |
| LP | platform_scale, creator_scale, burn_scale | sum = 1,000,000 |
| Vesting | TotalLockedAmount, CliffPeriod, UnlockPeriod, platform_vesting_scale | lock ≤ 80% |
| Token-2022 | BaseTokenProgram, TransferFeeBasisPoints | ≤ 500 bps |
| Quote | GlobalConfig | SOL or USD1 |
| Graduation | cpswap_config | 0.25% to 4% tiers |
| Brand | name, web, img | 64 / 256 / 256 bytes |
Bounds are read live from launch-mint-v1.raydium.io/main/configs and api-v3.raydium.io/main/cpmm-config each time the editor opens.
The curve
LaunchLab's constant-product curve starts from virtual reserves. With supply S, sold amount T, locked amount L and graduation target F, the migrated amount is M = S - T - L, and the reserves are a = T² / (T - M) and b = F·M / (T - M). After x tokens are sold the price is a·b / (a - x)². At graduation the price is F / M, which is the price the CPMM pool opens at.
Two things follow: the curve needs more tokens sold than migrated, and the graduation target scales every price on the curve by the same factor.
Curve types
The program knows constant-product, fixed-price and linear curves, but every public GlobalConfig on Solana today is constant product. The Quote node lists exactly the configs Raydium serves. When Raydium publishes a config of another type, it appears there.
