What lands where
Jupiter's Studio API builds and co-signs the create transaction and publishes the token's metadata when it sends it, so the create itself goes through Jupiter. Everything else is SOLTidy's Jito bundle: transaction 1 is your dev buy and SOLTidy's fee, then up to four buyer transactions with three wallets each (the last holds two plus the Jito tip). Jito runs them in order in one block, and if any of them would fail, none of them run.
The bundle is sent right after the create confirms, so it lands in the next blocks, not in the create's own block. Before sending, SOLTidy simulates every bundle transaction against the live curve; if someone else bought first and a buy would now break your slippage, nothing is sent and you can retry at the live price.
How the buys are priced
Every buy is quoted with Meteora's Dynamic Bonding Curve math, in bundle order: the dev buy on the fresh curve, then each buyer on the curve the earlier buys leave. Each buy pays the curve's 1% trading fee, half of which goes to you as the creator, and gets at least the tokens your slippage allows.
Example on the Meme preset: a 1 SOL dev buy plus 10 wallets buying 0.5 SOL each buy about 13% of the 1 billion supply and fill about 3% of the curve's 185 SOL target.
| Who | Pays |
|---|---|
| Your wallet | Create (≈ 0.028 SOL), dev buy, 0.3 SOL SOLTidy fee, token account rent |
| Each buyer wallet | Its buy plus ≈ 0.0043 SOL for its token account, temporary wSOL account and network fee |
| Tip payer (first wallet of the last transaction) | The Jito tip you set (default 0.001 SOL) |
Bundled buys are public
Anyone can see which wallets bought right after the create, and screeners like RugCheck and Bubblemaps flag the bundled share of supply. Bundle your own team or treasury wallets, say so publicly, and never use bundling to make a token look more popular or more widely held than it is. To create a token without bundling, use the Jupiter Studio Token Launcher.
Questions & answers
Why can't the create be in the bundle?
Jupiter signs the create transaction itself and publishes the token's metadata when it sends it, so it must go through Jupiter's Studio API. SOLTidy sends the bundle the moment the token exists.
What happens if the bundle doesn't land?
None of its transactions run: no buys, no SOLTidy fee, no tip. The token already exists, and the result screen offers to retry the buys at the live price with a fresh bundle.
How many wallets can buy?
Up to 11 besides yours. Jito accepts 5 transactions per bundle; your dev buy takes one and each buyer transaction fits three wallets (two in the last, next to the tip).
Are the buyer keys sent anywhere?
No. Keys are parsed and used to sign in this tab only, wiped right after signing, and never sent to SOLTidy or stored. Only the signed transactions go to Jito.
Do I need a dev buy?
No. With a dev buy of 0 the bundle's first transaction carries only SOLTidy's fee, and the buyer wallets buy first.
Is there a fee?
SOLTidy charges a flat 0.3 SOL per bundle launch, paid by your wallet inside the bundle's first transaction, so it's only charged if the bundle lands. Each buyer wallet pays its own buy and network fee; one of them pays the Jito tip.
