Jito Bundle
Transaction primitives
A Jito bundle is a group of up to five Solana transactions that a Jito block engine executes in order and atomically: either every transaction lands, or none does. A bundle carries a tip, paid to one of the Jito tip accounts, that sets how it ranks in the block engine’s auctions. Bundles only matter when a Jito-Solana validator is the leader.
Detailed explanation
A bundle exists to give a sender two things a single transaction cannot: a guaranteed order across several transactions, and an all-or-nothing result. The block engine runs the transactions one after another in the order you give. If any of them fails, none of them is committed.
Each bundle carries a tip, which is an ordinary SOL transfer to one of the eight Jito tip accounts. You can fetch them with getTipAccounts. The tip is what the auctions rank on, and the docs recommend putting it in the main transaction so a failed transaction does not pay it. Do not put tip accounts in an address lookup table, because the tip then has no effect.
Jito runs parallel auctions at 50 millisecond ticks and passes the highest-paying combination of bundles to the validator, up to a compute limit. The minimum tip is 1,000 lamports, and the documentation warns that this may not be enough when demand is high.
Two limits are worth knowing. A bundle holds at most five transactions. And tips do not prioritise anything for a leader that is not running Jito-Solana, so a bundle only helps when the current leader does. Searchers, arbitrage bots and any bot that wants an atomic send use bundles for these reasons.
When you'll see this
You see bundles in sendBundle and bundle-status calls on a block engine endpoint, in searcher and MEV bot code, and in the tip transfers visible on chain.
How NoLimitNodes uses this
We do not run a block engine, but our Shredstream and Yellowstone gRPC feeds supply the data searchers build bundles from. The MEV bots we build include the bundle builder, the tip policy and the retry rules.
Related terms
- Jito Tip · A SOL transfer to a Jito tip account that pays the block engine to include and order your transaction bundle.
- Block Engine · The Jito service that receives bundles, runs auctions for block space and passes the winners to the leader.
- Atomic Transaction · A transaction that completes in full or has no effect. If one instruction fails, every change is rolled back.
- Backrun · A transaction that runs right after another to use the state that one leaves behind, most often to arbitrage a price gap.
- Compute Unit Budget · The CU limit and price you set with the ComputeBudget program to control how much work and priority fee a transaction uses.