Jito bundles
Jito bundles: atomic execution on Solana
A Jito bundle is up to five Solana transactions that execute atomically and in order, in one block, or not at all. A tip auction prices inclusion. This guide covers how bundles work, how to price tips, why they fail and how to submit them.
How the pieces fit
Jito-Solana is a modified validator client. Validators running it accept bundles through the Jito Block Engine, an off-chain auction. A searcher attaches a tip, a SOL transfer to one of eight tip accounts, conventionally in the bundle's last transaction. The Block Engine simulates each bundle and hands the winners to the leader, to be included atomically and in order.
Three things follow for a trading system. Bundles land only when a Jito-running validator leads, so plan for waiting several slots. One failing transaction drops the whole bundle silently, so simulate first. And tips are a market, so price them live and never hard-code them.
Pricing tips without overpaying
The floor is 1,000 lamports, but a floor bid is not a strategy. Poll the Block Engine's tip-floor endpoint for live percentiles, peg routine flow around the middle of the range, and bid toward the top only when the trade justifies winning a contested slot: launches, liquidations, oracle updates. Calm periods clear in the tens of thousands of lamports; in a hot moment the clearing price can rise a thousandfold in seconds.
Why bundles fail
- Simulation failure
- Any transaction reverts and the bundle is dropped, with no trace on-chain.
- Outbid
- Your tip lost the auction for that leader's slots.
- Blockhash expiry
- The bundle waited too long for a Jito leader. Use a fresh blockhash and resubmit.
- Structure
- More than five transactions, the tip outside the last one, or a transaction repeated across pending bundles.
Submitting bundles
You can call Jito's public Block Engine directly; its endpoints are shared and rate-limited. AllenHark Relay takes a bundle of up to five transactions over QUIC, WebSocket or HTTPS, with a Jito tip of at least 1,000 lamports in the last one. Slipstream, a separate product billed in tokens, also supports bundles and works with any sender.
Go deeper
- How to send Jito bundles on Solana
Block Engine mechanics, the tip auction and working code for HTTPS, QUIC and WebSocket.
- Understanding Jito bundles and block building
Why atomicity matters and how block building changes execution strategy.
- AllenHark Relay docs
The bundle endpoint: request format, QUIC frames, error codes and tip rules.
- Solana MEV relay services compared
Where relays fit in the submission stack and how the options differ.
Frequently asked questions
What is a Jito bundle?
Up to five Solana transactions sent together to the Jito Block Engine. They execute atomically and in order: all of them land in one block, in sequence, or none do. Validators running the Jito-Solana client include bundles through an auction in which searchers bid with tips. Atomicity is the point: multi-leg arbitrage, protected snipes and any strategy that loses money on a partial fill.
How much should I tip for a Jito bundle?
There is no fixed number: tips are an auction and the market moves. The floor is 1,000 lamports. Calm periods usually clear in the tens of thousands of lamports; launches and liquidations can push winning tips into the millions. Read Jito's tip-floor API for live percentiles, price routine flow around the middle of the range, and go higher only when the trade must win.
Why is my Jito bundle not landing?
In order of likelihood: the tip is below the market for that leader; one transaction fails simulation, which drops the whole bundle; the blockhash expired while waiting for a leader running Jito-Solana; the bundle has more than five transactions; or the tip is not in the last transaction. Silent drops are usually a simulation failure, so simulate each transaction first.
Do I need my own connection to the Jito Block Engine?
No. Jito's public Block Engine endpoints are open to anyone, but they are shared and rate-limited. A relay such as AllenHark Relay takes your bundle over QUIC, WebSocket or HTTPS and forwards it for you, so you do not manage the connection yourself.
Jito bundles vs priority fees — which should I use?
They solve different problems. A priority fee raises a transaction's scheduling priority but gives no atomicity and no ordering against other transactions. A bundle guarantees atomic, ordered execution and pays the block builder directly through its tip. Use priority fees for ordinary single transactions and bundles when order or all-or-nothing matters. Many systems use both.