What Is a Jito Bundle on Solana? Atomic Execution & MEV Protection Explained
If you've ever launched a token, sniped a listing, or swapped on a Solana DEX, you've probably seen a field labeled "Jito Tip" somewhere in the interface. Most people type in a number and move on without thinking about it.
But behind that small input field is one of the most important pieces of infrastructure on Solana — and understanding it can be the difference between a successful trade and a lost one.
This guide covers everything: what a Jito Bundle is, how it works under the hood, and the two core reasons it exists.
What Is a Jito Bundle?
A Jito Bundle is a group of up to 5 Solana transactions that are executed together as a single unit.
Three guarantees:
- Sequential: Transactions execute in the exact order you define — first Transaction 1, then 2, then 3.
- Atomic: Either all transactions succeed, or none of them are committed to the blockchain. If Transaction 3 fails, Transactions 1 and 2 are rolled back as if they never happened.
- Same block: Every transaction in the bundle lands in a single Solana block, confirmed at the same time — not spread across multiple blocks or multiple seconds.
That's it. Simple concept, massive implications.
Jito Bundles are built and maintained by Jito Labs. As of 2025, about 95% of Solana's total stake runs the Jito validator client, which means bundles are processed in nearly every block.
Why Jito Bundles Exist
Jito Bundles solve two fundamentally different problems: atomic sequential execution for multi-transaction operations, and MEV protection against sandwich attacks. Understanding both is the key to understanding why they're everywhere on Solana.
1. Atomic Sequential Execution in a Single Block
On Solana, individual transactions are atomic — all instructions inside a single transaction either succeed or fail together. But the moment you need more than one transaction, you lose that guarantee.
If you submit Transaction A and Transaction B separately:
- A might succeed while B fails.
- B might execute before A.
- They might land in different blocks at different times.
For basic token swaps, this doesn't matter. But for anything more complex, it's a serious problem.
Token Launches and Multi-Wallet Sniping
When launching a memecoin on platforms like Pump.fun, creators typically want to secure initial token supply across multiple wallets before anyone else can buy in. Bundling the launch and the first buys from multiple wallets into a single Jito Bundle makes this possible.
With a Jito Bundle, the creator packages everything into one atomic unit:
- Transaction 1: Create the token
- Transaction 2: Wallet A buys
- Transaction 3: Wallet B buys
- Transaction 4: Wallet C buys
All four transactions land in the same block, in exact order. Because the bundle is atomic, no external transaction can be inserted between the token creation and the first buys — sniper bots cannot detect and front-run the launch. The creator secures the initial supply at the lowest price, and the buying pressure across multiple wallets pushes the price up from the very first block.
If any of the buy transactions fail (insufficient balance, wrong parameters), the entire bundle is rolled back — including the token creation. Nothing happens on-chain. The creator can fix the issue and try again without leaving a token live with no initial holders.
Multi-Step Transaction Chains
Jito Bundles are widely used in automated bot operations where multiple transactions must execute as a single unbreakable sequence.
For example, bots that increase unique trading wallets or grow the number of token holders operate by cycling through a series of dependent steps within one bundle:
- Transaction 1: Fund a new wallet with SOL
- Transaction 2: New wallet buys a token
- Transaction 3: Transfer the purchased token to main wallet
- Transaction 4: Recover remaining SOL from the new wallet
- Transaction 5: Pay service fees
Each step depends on the previous one. Without a bundle, a failure at Transaction 2 leaves the SOL from Transaction 1 stranded in the new wallet, requiring manual recovery. With a Jito Bundle, either all five transactions succeed or nothing happens on-chain.
Buying Across Multiple Wallets in a Single Block
When buying an existing token with multiple wallets, bundling all purchases into a single block ensures no external transaction can execute between each wallet's buy. Without a bundle, other traders or bots can see the first wallet's purchase and react before the remaining wallets execute — front-running the rest of the buys or driving the price up further.
With a bundle, the entire sequence is private and atomic. All wallets buy in exact order within the same block, and the trades appear as independent buying activity from separate wallets.
2. MEV Protection
The second reason Jito Bundles exist is MEV protection — specifically, protection against sandwich attacks.
What Is MEV?
MEV stands for Maximal Extractable Value. It refers to the profit that can be extracted by reordering, inserting, or excluding transactions within a block.
On Solana, the most common form of MEV that affects regular users is the sandwich attack.
How a Sandwich Attack Works
When you submit a regular swap transaction on Solana, it enters the network's transaction pipeline where it can be observed by MEV bots before it's included in a block.
Here's what happens:
- You submit a swap: Buy 1 SOL worth of Token X.
- A MEV bot sees your pending transaction. It calculates that your buy will push Token X's price up.
- The bot front-runs you: It buys Token X before your transaction, at the lower price.
- Your transaction executes: You buy Token X at a now-higher price because the bot's purchase already moved the price.
- The bot back-runs you: It immediately sells Token X after your transaction, profiting from the price difference.
You got a worse price. The bot pocketed the difference. This happens automatically, thousands of times per block, and the victim usually never notices — they just think "slippage was high."
How Jito Bundles Reduce the Risk
When you send a transaction through a Jito Bundle, it bypasses the public transaction pipeline and goes directly to the Jito Block Engine — a private system where MEV bots cannot observe your transaction. It goes straight from your application → Block Engine → Jito validator → on-chain execution, with no exposure to the public mempool at any point.
Since the attacker never sees your transaction, they cannot insert trades before or after yours. The vast majority of sandwich attacks are effectively blocked.
This is why Jito Bundles are standard for operations like bulk selling across multiple wallets and market making bots that repeatedly trade the same token to build chart activity. In both cases, every transaction stays hidden from MEV bots until it is confirmed on-chain.
Jito also provides additional countermeasures like the jitodontfront mechanism, which forces your transaction to appear first in any bundle it's included in — adding another layer of front-running protection.
Routing swaps through Jito Bundles is far safer than submitting transactions through a regular RPC, and is the most widely adopted MEV protection on Solana today.
Jito Bundle vs. Regular Transaction
The following table summarizes the key differences between submitting a regular Solana transaction and using a Jito Bundle:
| Regular Transaction | Jito Bundle | |
|---|---|---|
| Max transactions | 1 | Up to 5 |
| Execution order | Not guaranteed | Guaranteed sequential |
| Atomicity | Single tx only | All-or-nothing across all txs |
| MEV protection | None — visible in mempool | Bypasses mempool, significantly harder to attack |
| Priority mechanism | Priority fee | Jito Tip (auction) |
| Failed bundle cost | Gas fee paid regardless | Tip only paid if landed |
| Validator coverage | All validators | ~95% of Solana stake |
For any operation that involves multiple transactions or requires protection from MEV, Jito Bundles are the standard on Solana.
How the Jito System Works
Here's what happens behind the scenes when you use a Jito Bundle:
- Step 1: Bundle Creation: Your application creates up to 5 signed transactions and packages them into a bundle, with a tip attached.
- Step 2: Block Engine: The bundle is sent to Jito's Block Engine — not to a regular Solana RPC. The Block Engine collects bundles from thousands of users simultaneously.
- Step 3: Simulation: The Block Engine simulates every transaction in your bundle. If any transaction would fail, the entire bundle is rejected before it touches the blockchain. You don't pay anything.
- Step 4: Auction: Every ~200 milliseconds, the Block Engine runs an auction. Bundles compete based on their tip amount. Higher tip = higher priority. The winning bundles are forwarded to the current Jito validator.
- Step 5: Execution: The Jito validator executes the winning bundles atomically. All transactions succeed and are committed, or the bundle is discarded entirely.
What Are Jito Tips?
A Jito Tip is a small SOL payment attached to your bundle. It is the cost of submitting your bundle to the Jito Block Engine — paid to validators as an incentive to include your bundle in the next block.
- Minimum: 1,000 lamports (0.000001 SOL)
- Only paid if your bundle lands on-chain. Failed simulations or lost auctions cost nothing.
- The tip is paid per bundle, not per transaction — a bundle with 5 transactions pays the same tip as a bundle with 1.
How to Approach Tipping
A well-built platform constructs transactions correctly, uses proper simulation, and handles retries internally — meaning even the minimum tip is often enough to land your bundle successfully under normal network conditions. If you find yourself needing high tips just to get basic operations through, the issue is more likely the platform's transaction construction than the tip amount.
Start with the lowest tip possible and only raise it when necessary:
| Scenario | Suggested Starting Tip |
|---|---|
| Normal conditions | 0.000001 SOL (minimum) |
| Moderate congestion | 0.0001 – 0.0005 SOL |
| Competitive token launch | 0.001 – 0.005 SOL |
| Extremely contested snipe | 0.005+ SOL |
The goal is to pay the least amount necessary for your bundle to land. Overpaying tips is wasted SOL.
Summary
Jito Bundles serve two purposes:
- Atomic sequential execution — Group multiple transactions into one all-or-nothing package. Used for token launches with multi-wallet buys, generating on-chain trading activity in a single block, and any multi-step operation where partial failure is unacceptable.
- MEV protection — Bypass the public transaction pipeline so MEV bots can't observe your swaps. Blocks the vast majority of sandwich attacks by keeping your transactions hidden until they are confirmed on-chain.
Both features are powered by the Jito Block Engine and Jito Tips, with ~95% of Solana validators supporting bundle processing.