Docs

Jup Pad launches real Jupiter Studio coins. A launch is five steps, and only the payment needs a transaction from the creator.

1. 1

   Sign in POST /auth/nonce, POST /auth/verify

   The creator signs a one-time message (not a transaction) to prove wallet ownership. Jup Pad returns a session.

2. 2

   Submit the launch POST /launches

   The launch settings (starting market cap, graduation target, trading fee, anti-sniping, vesting, fee preset) and the artwork. Jup Pad validates them, checks the curve against Studio's minimum raise with Studio's own simulation, pins the artwork, and returns the launch fee and treasury.

3. 3

   Pay the launch fee Creator wallet

   The creator signs one SOL transfer to the Jup Pad treasury. The payment is signed once and saved before it is sent.

4. 4

   Confirm the payment POST /launches/:id/confirm

   Jup Pad verifies the transfer on Solana. One payment can only pay for one launch.

5. 5

   Jup Pad launches the coin Jupiter Studio

   From its own per-coin deployer wallet, Jup Pad builds the Jupiter Studio launch, checks the transaction against an instruction allowlist, signs, and submits it with the artwork. Jupiter lands it and creates the coin's Studio page. The fee preset is frozen once the pool exists.

Studio requests go through the Jup Pad backend. It holds the Jupiter Studio API key, so the browser never sees it.

1. The pool trading fee

Every trade in a Studio pool pays a trading fee of 1% or 2%, chosen at launch. It is part of the pool and enforced on-chain.

2. The creator fee share

40% of the trading fee is the creator fee share. Measured on mainnet: Meteora keeps 20% as a protocol fee and the rest is split evenly between the creator fee share and Jupiter. The creator fee share accrues in the pool until it is claimed.

3. The keeper claims it

Jup Pad launches each coin from its own deployer wallet, which makes that wallet the pool's creator. Jup Pad's keeper uses it to claim the creator fee share on a regular schedule, once the unclaimed amount is worth a claim transaction, then routes it by the coin's preset. Every claim and transfer is published in the coin's public fee ledger.

4. The Jup Pad platform fee

Before routing, Jup Pad keeps 20% of the claimed creator fee share as its platform fee. It is the same in every preset and comes from the backend preset weights. The rest is routed to holders, the creator, and buyback by the preset.

5. How the product shows percentages

Routing percentages are shares of the full claimed creator fee share, including Jup Pad’s platform fee. The Holders preset shows Holders 70% and Creator 10% and Jup Pad 20%.

Worked example. 100 SOL of trading volume at a 1% fee pays 1 SOL in trading fees. The creator fee share is 0.4 SOL. The platform fee is 0.08 SOL. With the Holders preset, holders receive 0.28 SOL (70% of the creator fee share), the creator 0.04 SOL (10%), and Jup Pad 0.08 SOL (20%).

In a coin's fee ledger, claim amounts are the full amount the keeper claimed, including the platform fee. Transfers list every destination, including Jup Pad. The launch fee you pay when launching is separate and shown before you pay.

Each coin launches with one of three live presets. The percentages are shares of the full creator fee share, including the platform fee.

• HoldersFrozen at launch

  Most of the creator fee share is paid to holders pro rata, with a slice to the creator.

  • Holders70%
  • Creator10%
  • Jup Pad20%

• BalancedFrozen at launch

  Holders and the creator receive equal parts of the creator fee share; a slice buys back and burns the coin.

  • Holders35%
  • Creator35%
  • Jup Pad20%
  • Buyback and burn10%

• CreatorFrozen at launch

  Most of the creator fee share is credited to the creator; a slice buys back and burns the coin.

  • Creator70%
  • Jup Pad20%
  • Buyback and burn10%

Frozen at launch. Jup Pad launches the coin from its own deployer wallet so its keeper can claim the creator fee share and route it by this preset. The preset cannot be changed after launch. Every claim and transfer is published in the coin's ledger.

Holder and creator payouts are made in the coin's pair asset. Buyback and burn swaps the routed amount into the coin through Jupiter and burns it.

Every fee route says who makes it happen. There is no generic verified badge.

Keeper routed

Jup Pad's keeper claims the creator fee share from the launch program and sends each recipient's part. The split is fixed at launch and every transfer is published, but the transfers are a Jup Pad service, not an on-chain rule.

Examples: Every Jup Pad fee preset: claiming the creator fee share, paying holders, crediting the creator, buyback and burn.

Wallet claimed

Fees accrue in the launch program. Only the creator's wallet can claim them, by signing a claim transaction.

Examples: Coins launched outside Jup Pad. Their creator fee share stays in the pool until the creator's wallet signs a claim.

On-chain

The launch program itself enforces this rule. No keeper or signature is involved.

Examples: The Studio pool trading fee, the bonding curve, vesting, and the liquidity lock at graduation.

Keeper routing is a Jup Pad service, not an on-chain rule. It is never labeled as program enforced.

With the Holders and Balanced presets, the keeper pays the holders' part pro rata to current holders, in the pair asset, on each run. Holders do not claim and do not pay a network fee.

Pools, Jup Pad wallets and program accounts are excluded from the holder set. Shares too small to send accrue until they are worth a transfer.

Explore lists Jupiter Studio launches as one market. Coins launched with Jup Pad show their frozen preset and keeper-routed fees. For every other coin, the creator fee share is claimed by the creator's own wallet.

• More fee presetsBuyback, Community treasury, Custom, Stock basket are designed but cannot be launched yet. Only Holders, Balanced, and Creator are live.
• Dev buyBuying your own coin as part of the launch transaction is not available yet.
• Platform analytics and holder reward balancesAnalytics use recorded launches, indexed trades and keeper ledgers. Holder rewards use signed-in payout and accrual records. Amounts retain their asset units; missing historical USD values are not estimated.
• NotificationsLaunch reminders are kept in your browser. No email or push notification is sent.

• Pair assets are SOL, USDC, and JUP. No arbitrary pair asset mints.
• No custom Token-2022 transfer hooks.
• No hard trading rules such as max wallet or sell taxes enforced on every trade.
• No instant direct DAMM launch.
• No change to a coin's fee preset after launch. The preset is frozen at launch.
• A website cannot enforce rules on trades made elsewhere. Anything Jup Pad shows as policy applies only to what Jup Pad itself executes.

Jup Pad runs on Solana mainnet. Discovery, prices, charts, trades, and holders come from Jupiter's live index. Swaps go through Jupiter Ultra. Launches go through the Jup Pad backend, which creates the coin through Jupiter Studio after you pay the launch fee. You approve every transaction in your own wallet.

• WalletAny Solana Wallet Standard wallet in your browser: Phantom, Backpack, Solflare, Jupiter, and others. Keys never leave the wallet.
• DiscoveryJupiter Studio launches, refreshed every few seconds: new, graduating, and graduated, with real artwork.
• Coin pagesLive price, candles, trades, holders, and safety checks from Jupiter's index and Jupiter Shield.
• SwapsJupiter Ultra quotes with your wallet as taker. You sign, Ultra lands the transaction.
• LaunchSign in, submit the launch, pay the launch fee; Jup Pad creates the coin through Jupiter Studio.
• Fee presetsHolders, Balanced, or Creator. Jup Pad's keeper claims the creator fee share on a regular schedule and routes it by the preset; every transfer is published.
• Scheduled launchesChoose a future time and pay the launch fee now to authorize execution. The worker runs the launch when due, even with your browser closed. Change the time or cancel before execution starts; paid fees are not refunded.
• Creator feesReal Studio fee pools. For Jup Pad launches the creator's part is credited to the creator, who withdraws it from Earnings.

What the backend needs before the remaining features can go live.

• Dedicated RPC

  Set NEXT_PUBLIC_SOLANA_RPC_URL to a Helius, Triton, or similar endpoint. The public fallback works but is rate limited.

• Jupiter API rate limits

  Market-data and swap requests use Jupiter's rate-limited public APIs. Studio pool, fee and claim requests use Jup Pad's backend service. Retry unavailable fee data when the service recovers.

• Undocumented data API

  Discovery, trades, holders, and charts use datapi.jup.ag, the API behind jup.ag. It is not documented and can change; responses are validated defensively.

• Jup Pad API

  Set NEXT_PUBLIC_PAD_API_URL to the Jup Pad backend. Launches, sign-in, payment confirmation, Studio requests, and fee ledgers go through it.

• Indexer and distributor APIs

  Platform analytics and creator earnings use public backend endpoints. Holder balances use the signed-in rewards endpoint. Trading totals cover indexed transactions; paid schedules execute on the server at or after the selected time. Older browser reminders do not execute launches.