How Same-Block Bundling Works on Solana

Every new token on a bonding-curve platform like pump.fun starts the same way: it doesn't exist, and then it does. That transition — the moment a mint account is created and the first buy lands — is the single most contested moment in the token's life. Same-block bundling exists because ordinary transactions can't guarantee where you land in that moment, and on Solana, milliseconds decide who gets the first price.

The problem: a gap between creation and ownership

If you submit a token-creation transaction and then a separate buy transaction right after it, those are two independent events on the network. Between them there's a window — however small — where the token exists but you don't yet own any of it. On a fast chain like Solana, that window might be a fraction of a second. It's still enough time for an automated bot watching new mint activity to see the token, submit its own buy, and get included in an earlier or same slot than your second transaction.

This isn't a hypothetical. Bots that watch for new pump.fun mints are common, and they don't need much of a head start to buy ahead of a manual multi-step launch.

What a Jito bundle actually is

Jito is a Solana validator client that accepts bundles: a group of up to five transactions that are submitted, ordered, and executed together, atomically. Atomic means all-or-nothing — either every transaction in the bundle lands in the same block in the exact order you specified, or none of them do. There's no partial execution and no way for another transaction to be inserted between yours.

That's the mechanism that closes the gap described above. If your token-creation transaction and your buy transactions are all part of one bundle, there is no moment where the token exists without you already owning part of it — because the whole bundle either happens at once or not at all.

How the bundle gets prioritized

Bundles compete for inclusion the same way transactions do, through a tip paid to the block-producing validator. Jito bundles include a tip transaction, typically the last transaction in the bundle, that pays a validator running Jito's software to include the bundle. Higher tips generally land more reliably during busy periods; during quiet periods a small tip is often enough. This is a separate cost from ordinary Solana network fees, which still apply to every transaction in the bundle regardless of the tip.

What "same block" actually guarantees

It's worth being precise about what this does and doesn't promise:

• It guarantees your bundle's transactions execute in order, with nothing else interleaved between them.
• It does not guarantee the bundle lands at all — if the tip isn't competitive enough, or network conditions change, the bundle can be dropped, in which case none of the transactions execute and you keep your funds minus whatever fees were spent on the attempt.
• It does not prevent someone from buying the token in a later block, once it's public. It only removes the specific gap between creation and your own first buy.

Why this matters more on Solana than on some other chains

Solana's block times are short — around 400 milliseconds — and its mempool works differently from Ethereum's. Transactions propagate to leaders quickly, which is generally good for user experience, but it also means the window for automated actors to react to new activity is compressed rather than eliminated. Bundling doesn't fight the speed of the network; it uses the same block-level atomicity the network already provides.

Where this fits into a launch

In practice, same-block bundling is one piece of a launch, not the whole thing. You still need to decide how many wallets to buy from, how much SOL to commit, and what tip to set. Those are covered in our guides on choosing wallet count and setting the right Jito tip.