Jito Tip
Transaction primitives
A Jito tip is a plain SOL transfer to one of eight Jito tip accounts, included as the last instruction in a bundle. The tip tells the Jito block engine "if you land this bundle, I pay this much." Validators running the Jito client receive a share of tips from bundles they include. Tips are the priority fee mechanism for atomic bundles.
Detailed explanation
The Jito block engine accepts bundles of up to five transactions. A bundle is atomic: every transaction lands in the same slot or none of them do. Searchers use bundles for arbitrage, liquidations, and protected execution. The mechanism that makes bundles competitive is the tip.
Tips are paid by including a System Program transfer to one of the eight tip accounts. Their pubkeys are published in the Jito docs and rotate occasionally. The tip transfer must be in one of the bundle's transactions, and it must be a transfer to a known tip account. Jito's engine reads the total tip amount across the bundle and sorts bundles in priority order.
Tip math is different from CU pricing. A high CU price helps you land in any leader's block. A high Jito tip only helps when the leader is running the Jito client (about half of mainnet stake). The right play during congestion is usually both: set a reasonable CU price so non-Jito leaders include you, and tip enough that Jito leaders pick you over competing searchers.
One opinion: most application teams do not need bundles at all. They need a clean RPC, a sensible CU price, and a reliable submit path. Bundles are a searcher tool. Reach for them only when atomicity actually matters.
When you'll see this
Tip transfers show up as System Program transfers to one of the published Jito tip accounts. You will see them at the end of bundles submitted via the Jito Block Engine RPC. On a Geyser stream, watching the tip accounts is a clean way to measure searcher activity in real time.
How NoLimitNodes uses this
Our gRPC nodes can be subscribed directly to the Jito tip account writes for live tip-rate analysis. For builders running searcher pipelines, our RPC nodes handle the simulate-and-submit path with low jitter.
Related terms
- 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.
- Durable Nonce · A System Program nonce account that lets a transaction stay valid past the 150-slot recent-blockhash window.
- Processed, Confirmed, Finalized · The three Solana commitment levels, ordered from "this validator saw it" to "supermajority will not roll it back."
- Slippage · The gap between the price you quoted and the price you actually got, set as a tolerance on every swap instruction.
- Yellowstone gRPC · The Triton-built Geyser plugin that exposes a gRPC stream of accounts, transactions, and slots over the wire.