How a Jupiter Studio launch works
Jupiter Studio runs on Meteora's Dynamic Bonding Curve (DBC) program. Each Studio launch creates its own DBC config, a vanity mint address from Jupiter and the token's pool, in one transaction that Jupiter's Studio API builds and co-signs. Your wallet is the only missing signature. SOLTidy asks the API for that transaction exactly as jup.ag/studio does, checks that your wallet pays for it, that it only calls the bonding curve, Jupiter's creator program and system programs, and simulates it before you approve.
Because Jupiter publishes the token's metadata when it sends the create, the create goes through Jupiter. SOLTidy's own transaction, holding the dev buy and the fee, is signed before anything is sent and broadcast the moment the pool exists, usually a few seconds later.
The curve, fees and graduation
SOLTidy launches Studio tokens on SOL-priced curves, so the dev buy spends SOL directly. Every trade on the curve pays a 1% fee, and half of it goes to you as the creator. Jupiter's anti-sniping fee (which starts at 99%) is turned off, since it would also hit your own dev buy. When the curve has raised its target, about 185 SOL on the Meme preset, its liquidity moves into a Meteora DAMM v2 pool and trading continues there.
The dev buy is quoted with Meteora's own curve math on the exact curve in Jupiter's transaction. Your max slippage covers anyone who buys in the seconds between the create and your buy: if the price moves further, the buy fails, the fee is not charged, and you can retry at the live price.
| Item | SOL |
|---|---|
| Create (rent and network fee, Jupiter charges no fee) | ≈ 0.028 |
| Dev buy (curve fee included), about 24.2M tokens, 2.4% of supply | 1 |
| SOLTidy fee | 0.1 |
| Your token account rent (returned if you ever close it) | ≈ 0.0015 |
Launching with more wallets
To have several of your own wallets buy right after the create in one block, use the Jupiter Studio Bundle Launcher. To buy or sell an existing Studio token from many wallets, use Jupiter Studio Mass Buy and Mass Sell.
Questions & answers
Is this a real Jupiter Studio token?
Yes. It is created by Jupiter's Studio API with Jupiter's config and vanity mint, its metadata and page are published by Jupiter, and it shows up on jup.ag like any Studio launch.
Why does my wallet ask me to sign a message?
Jupiter Studio's API only builds a create transaction for a wallet that has signed its sign-in message (a timestamp and a random code). Signing a message costs nothing and can't move funds.
Why isn't the dev buy in the same transaction as the create?
Jupiter's create transaction is already signed by Jupiter, so nothing can be added to it, and it has to be sent through Jupiter so the metadata is published. SOLTidy signs the dev buy beforehand and sends it as soon as the token exists.
What if the dev buy fails?
The token still exists, no SOLTidy fee is charged (the fee is in the dev buy transaction), and the result screen offers to retry the buy at the live price.
Can I launch on Bags or Moonit here?
No. Bags launches must be signed by Bags' own token-creation authority through its API key, and Moonit launches are co-signed by Moonit's backend, so neither can be created outside their apps. SOLTidy can trade both: see Bags and Moonit Mass Buy.
Is there a fee?
SOLTidy charges a flat 0.1 SOL per launch, paid in the same transaction as your dev buy, which is sent only after the token exists. Jupiter Studio charges no create fee; the create costs about 0.028 SOL of rent and network fees.
