Guide Hub · Updated July 2026

Jito Bundles: Atomic Execution on Solana

A Jito bundle is a group of up to five Solana transactions that execute atomically, in order, in a single block — or not at all. Inclusion is priced by a tip auction. This hub covers how bundles work, how to price tips, why bundles fail, and the fastest ways to submit them.

How the pieces fit

Jito-Solana is a modified validator client run by a large share of Solana stake. Validators running it accept bundles through the Jito Block Engine, an off-chain auction house: searchers attach a tip (a SOL transfer to one of eight designated tip accounts, conventionally in the bundle's last transaction), the Block Engine simulates each bundle, and winning bundles are handed to the leader for inclusion — atomically and in order.

Three properties follow that matter to a trading system: bundles only land when a Jito-running validator is the leader (plan for multi-slot latency); a single failing transaction drops the whole bundle silently (simulate first); and tips are a market (price them dynamically, never hardcode).

Pricing tips without overpaying

The tip floor is 1,000 lamports, but a floor bid is not a strategy. Poll the Block Engine's tip-floor endpoint for live percentile data and peg routine flow at the 50th–75th percentile, escalating toward the 95th+ only when the trade justifies winning a contested slot — launches, liquidations, oracle updates. During calm periods that means tens of thousands of lamports; in hot moments the clearing price can jump three orders of magnitude in seconds.

Why bundles fail

  • Simulation failure — any transaction reverts, the bundle is dropped with no on-chain trace.
  • Outbid — your tip lost the auction for that leader window.
  • Blockhash expiry — the bundle waited too long for a Jito leader; use a fresh blockhash and consider resubmission logic.
  • Structural errors — more than five transactions, tip not in the final transaction, or duplicate transactions across pending bundles.

Submitting bundles fast

You can call the public Block Engine directly, but shared endpoints add jitter exactly when you can least afford it. AllenHark Relay keeps persistent, co-located connections to the Block Engine and accepts sendBundle over HTTPS or QUIC — QUIC's 0-RTT resumption typically saves a round trip on every submission. For single (non-bundle) transactions that just need to land in the current slot, Slipstream handles sender-agnostic routing with protocol fallback.

Go deeper

How to Send Jito Bundles on Solana

The full 2026 guide: Block Engine mechanics, tip auction, dual-tip rules, and working code for HTTPS, QUIC, and WebSocket submission.

Understanding Jito Bundles & Block Building

Concepts first: why atomicity matters, front-running protection, and how block building changes execution strategy.

AllenHark Relay docs

sendBundle endpoint reference — request format, QUIC frames, error codes, and dual-tip validation rules.

Solana MEV Relay Services Compared

Where relays fit in the submission stack and how the major options differ on latency and reliability.

Frequently asked questions

What is a Jito bundle?

A Jito bundle is a group of up to five Solana transactions submitted together to the Jito Block Engine that execute atomically and in order: either every transaction in the bundle lands in the same block in the given sequence, or none of them land at all. Validators running the Jito-Solana client include bundles through an off-chain auction where searchers bid with tips. Atomicity is what makes bundles valuable — multi-leg arbitrage, sniping with protection, and any strategy where partial execution loses money.

How much should I tip for a Jito bundle?

Tips are a competitive auction, so there is no fixed correct number — the market moves with activity. As a working baseline: the floor accepted is 1,000 lamports, routine inclusion in calm conditions typically clears in the 10,000–100,000 lamport range, and competitive moments (token launches, liquidation cascades) can push winning tips to millions of lamports. Poll Jito's tip-floor API for live percentiles and price against the 50th–75th percentile for normal flow, higher when you must win the slot.

Why is my Jito bundle not landing?

The most common causes, in order: the tip is below the current market for that leader slot; a transaction in the bundle fails simulation (the whole bundle is dropped); the blockhash expired before a Jito leader rotated in — only validators running Jito-Solana can include bundles, so a bundle may wait several slots; the bundle exceeds five transactions; or the tip transfer isn't in the last transaction of the bundle. Persistent silent drops usually mean a simulation failure you're not seeing — simulate every transaction individually first.

Do I need my own connection to the Jito Block Engine?

No. You can submit directly to Jito's public Block Engine endpoints, but they are shared and rate-limited. Relays like AllenHark Relay maintain persistent, co-located connections to the Block Engine and accept your bundle over HTTPS or QUIC — you get lower and more consistent submission latency without managing the connection, plus dual-path submission (bundle + standard TPU) where a strategy allows it.

Jito bundles vs priority fees — which should I use?

They solve different problems. Priority fees raise your transaction's scheduling priority within a block but give no atomicity and no ordering guarantee against other transactions. Bundles guarantee atomic, ordered execution and let you attach value directly to the block builder via tips. Use priority fees for ordinary single transactions; use bundles when execution order or all-or-nothing semantics are worth paying for. Many systems use both: priority fee on each transaction, wrapped in a tipped bundle.

Submit bundles through a co-located relay

Persistent Block Engine connections, HTTPS and QUIC submission, and 0-slot landing for everything else.

Relay documentationView pricing