Jupiter Studio Dynamic Bonding Curve launches

The short answer

Jupiter Studio creates a Dynamic Bonding Curve launch, hosts the token’s native metadata, and indexes the signed launch through its submit API. Trenchables exposes the official Meme and Indie presets so the curve and graduation terms are explicit before you sign.

What Studio is for

Studio creates a customizable Dynamic Bonding Curve quoted in USDC, SOL, or JUP. Its launch configuration can include anti-sniping, creator vesting, fee choices, and LP locking before the token graduates to a Meteora pool.

The official create flow also issues presigned uploads for the image and metadata. After the wallet signs, Studio’s submit endpoint indexes the token and preserves the dedicated launch page. Your job is still to verify the mint, curve terms, vesting, and transaction receipt.

Studio vs meme curve pads

• Presets. Meme and Indie profiles make the initial and migration market caps reviewable.
• Launch controls. Anti-sniping, vesting, fee selection, and LP locking are part of the DBC configuration.
• Graduation. Liquidity migrates to a Meteora pool after the configured threshold is reached.

Studio is still a curve launchpad, not an endorsement or a guarantee of liquidity. Any preset can produce a weak or malicious token. For aggregator mechanics after a token exists, read Jupiter and DEX routing.

In Trenchables Launch

1. Open /launch → Solana → Jupiter Studio.
2. Choose the Meme or Indie preset and upload the image and token metadata.
3. Connect a mainnet wallet and review the curve, vesting, fee, and LP-lock terms.
4. Sign locally; Trenchables submits the signed transaction to Studio for indexing and returns the real mint and signature.

Honest preflight

• Do the initial and migration market caps match the selected preset?
• Is anti-sniping enabled or disabled as expected?
• Are the vesting schedule and LP-lock choice acceptable?
• Did the receipt return the expected mint and an on-chain signature?

Primary and official sources