By Why a 50+ wallet launch needs two stages
A Jito bundle holds at most 5 transactions. That is enough for a launch and a few buys, but not for dozens of wallets. TokenBundle's PumpFun Bundle therefore splits the launch into two stages: one atomic Jito bundle in block 0, followed by a snipe wave of up to 50 more wallets.
The whole flow runs through a 6-step wizard, so token details, wallets, amounts and review happen before anything is sent.
Block 0: the atomic launch bundle
The first stage is a single Jito bundle that fits inside the 5-transaction limit. It lands whole or not at all - either every transaction in it executes together, or none of them does.
- The create transaction with the dev buy.
- Buys from up to 3 bundle wallets.
- A tip transaction paying a 0.01 SOL Jito tip from the dev wallet.
Simulation and multi-region sending
Before sending, the launch bundle is simulated. It is then sent to 5 Jito regions in parallel - Frankfurt, Amsterdam, New York, Tokyo and the global endpoint - so it reaches whichever block engine can include it first.
Because the bundle is atomic, sending it to several regions does not risk a partial launch. If it lands, all of it lands.
Atomicity also protects the creator from the worst failure mode of a manual launch: the token being created while the dev and bundle buys fail or land later behind other buyers. In block 0 the create, the dev buy and the bundle wallets' buys are one unit, so they either all execute in that order or none of them do.
The snipe wave after the launch lands
Right after the launch bundle lands, the snipe wave starts. Up to 50 more wallets each send their own single-wallet Jito bundle with a 0.005 SOL tip. These bundles are independent, so one snipe landing or not does not affect the others.
Counting the dev wallet, up to 3 bundle wallets and up to 50 snipe wallets, a single launch can involve more than 50 wallets.
Each snipe wallet pays its own tip and its own 1% platform fee inside its own bundle, so a snipe that does not land pays neither. Only the snipes that land are counted toward the launch's recorded spend.
Worst-case pricing for parallel snipes
Snipes run in parallel, and each buy moves the bonding curve price. If every snipe were priced against the curve as it looked right after launch, the later ones would fail with pump.fun's slippage error, TooMuchSolRequired.
To avoid that, each snipe buy is priced for the worst case - as if all the other snipes had landed first. That keeps a parallel wave from failing on slippage.
PNL tracking and local-validator testing
Every launch records each wallet's spend - the dev buy, bundle buys and the snipes that landed - so PNL on the Manage token page starts from the real launch cost.
On a local validator with pump.fun cloned, a test of create plus dev buy, 3 bundle wallets and 10 parallel snipes landed in full.
FAQ
- How many transactions fit in a Jito bundle? At most 5, which is why block 0 holds the create and dev buy, up to 3 bundle wallets' buys and a tip transaction.
- How many snipe wallets can a launch use? Up to 50, each sending its own single-wallet Jito bundle with a 0.005 SOL tip right after the launch lands.
- What happens if the launch bundle does not land? Nothing executes, because the bundle lands whole or not at all, and the 1% platform fee is only paid if it lands.
- Why do parallel snipes not fail on slippage? Each snipe is priced as if all other snipes landed first, which avoids pump.fun's TooMuchSolRequired error.
- What does the Randomize button do? It lowers each bundle and snipe amount by a random 0-15% so buys are not identical.
Coordinate your launch with TokenBundle.
Prepare wallets, review allocations and manage network-specific launch execution from one workspace.
Open Solana workspace