A launch makes a multipair: your token paired with up to four assets at once — tokenized stocks, gold, crypto majors or any token with a real pool (outside the catalog it is marked unverified). Every leg is its own Raydium CLMM pool, so the token trades on Raydium, Jupiter and DexScreener from the first second. There is no pool between the assets, and holding the token is not a claim on them.

{{ docs.curveIdea }}

{{ st.num }}

{{ st.title }}

{{ st.body }}

The launch bundle creates the Token-2022 mint with a supply of 1,000,000,000 and revokes the mint, freeze and both metadata authorities in the same transaction. Each leg then gets a pool, a one-sided position with that leg's share of the supply from the launch price up to the maximum tick, a lock with Raydium Burn & Earn that hands the fee keys to the program vault, and the creator's buy. The mint comes first; then each asset gets one transaction of its own that creates the pool, adds the position, locks it and makes the creator's buy, so the buy is the first trade in every pool. On mainnet the launch goes through Jito as one bundle that lands whole or not at all; registration follows as separate transactions. Without Jito (a devnet test mode only) the transactions go out one by one, and the launch page says so.

Liquidity is one-sided: only your token goes into the pools, and buyers bring the assets. That is virtual liquidity — it equals the starting market cap and is split by weight. The creator pays network rent, about 0.17 SOL per leg. PairsFun puts in no money.

The starting market cap (27.96 SOL, priced in dollars at launch) divided by the supply gives the dollar price. Each pool converts it through its own asset's price, then rounds to the pool's tick spacing, so legs can start up to about 1% apart. Asset prices come from each asset's own on-chain pool: Raydium's TWAP when there is one, otherwise an Orca or Meteora spot price that DexScreener and Jupiter both confirm within 3%. If no price passes, the launch is refused.

Pay with one asset — USDC or SOL. Jupiter converts it into the basket assets, and the router buys every leg strictly by weight, so every pool moves the same percent. It is one wallet prompt: a swap and the buy, sent in order. Up to 0.3% can stay in your wallet as basket assets. Baskets of more than 3 assets are bought one asset at a time, and you can always buy through a single leg. Selling works the same way in reverse and pays out in the basket assets.

Every swap pays a 1% pool fee; Raydium keeps 16% of it. On every Standard and Creator-tax token 70% of the rest goes to the creator — split among up to five recipients chosen at launch (wallets or fomo accounts; X, GitHub and Twitch accounts are coming soon) — and is paid in the assets the pools collect. The protocol's 30% splits into {{ sh.burn }} of the fee that buys back and burns $PAIRS and {{ sh.treasury }} for the treasury. Reward and Custom tokens: creator 0%, platform 100% → {{ sh.rBurn }} $PAIRS buyback-burn / {{ sh.rTreasury }} treasury; the 1%, 2% or 3% transfer tax goes to holders (Reward) or is split between holders and burn (Custom) — the holders' part is sold for the basket assets and paid in them to holders with $20+ of the token, pro rata to their balance, once a pot reaches max($50, 0.1% of market cap) — at most once per 10 minutes per asset, with no platform cut. A Creator-tax token pays its 1%, 2% or 3% transfer tax to the creator instead (labeled CREATOR TAX), on top of the same 70% creator fee. Anyone can trigger a collection from the locked positions, and the money can only move to the program vault. Until $PAIRS launches, the buyback share accrues on-chain.

Every token page lists what you can check yourself on Solscan: supply fixed at 1,000,000,000 with the mint authority revoked; no freeze authority; name, ticker and metadata link frozen; no hidden Token-2022 extensions; 99%+ of the supply placed in the pools at launch; every position locked with Raydium Burn & Earn; fee keys held by the program, not the creator. A failed check is shown in red, never hidden.

A Jito bundle holds five transactions. A launch takes one for the mint and one per asset: each asset transaction creates its pool, opens and locks the position and makes the creator's buy. A transaction is capped by size (1232 bytes), accounts (64) and the call trace (64 instructions including nested calls — locking four positions in one transaction takes 72), which is why every asset gets its own. So the anti-snipe buy rides in the launch bundle with any basket, one asset to four, and is the first trade in every pool. One-click basket buys work up to 3 assets (with three the buy goes out as two transactions in a row); with 4, buyers pick one asset at a time. Rent grows with every asset. A fifth asset would need a sixth transaction, which is why a basket stops at four.

{{ f.q }}

{{ f.sign }}

{{ f.a }}