Jito tips: what you are actually buying

A Jito tip is a bid to have your transactions executed together, in order, without an outside party being able to insert themselves between them. For a volume campaign that matters because predictable swaps are exactly what searchers hunt for. The tip is a real cost with real variance, and understanding what it does and does not protect is worth more than any vendor assurance about MEV.

Volion Research Updated Jul 30, 2026 4 sections

What a Jito bundle is

A Jito bundle is a group of Solana transactions submitted together with the guarantee that they execute in the order given, in the same block, all or nothing. You attach a tip to win inclusion, competing against other bundles for the same block space. If the bundle does not win, none of its transactions land. If it wins, no third-party transaction can be inserted between its members.

The all-or-nothing property is the useful part. An ordinary transaction sits in the open where anyone watching can see it coming and act first. A bundle is atomic: the sequence you specified is the sequence that executes, or nothing executes at all.

The tip is paid to validators through Jito's tip accounts and is separate from the Solana priority fee. Both can apply to the same activity: the priority fee bids for compute scheduling, the tip bids for bundle inclusion. Treating them as the same line item is a common way to underestimate campaign cost by a meaningful margin.

Bundles are also capped in size, which shapes campaign design. A fleet of hundreds of wallets does not go out as one bundle; it goes out as many, each carrying its own tip. Tip cost therefore scales with the number of bundles, not the number of transactions, and batching efficiency turns into a direct cost saving.

What the tip protects you from

It protects against sandwich attacks: a searcher seeing your pending buy, buying ahead of it to push the price up, letting your trade execute at the worse price, then selling into the bump you created. Every lamport extracted that way is money you spent that produced no benefit to your chart. Bundling removes the gap the attack needs, because nothing can be inserted between your transactions.

The attack only works when the attacker can see your order and act between your intention and its execution. Bundling closes that window. What bundling does not do is hide your activity: the transactions are still on chain, still readable, still attributable to a fleet by anyone analysing funding patterns. Bundling is protection against interception, not against observation, and the two get conflated in marketing copy constantly.

Whether the protection is worth its tip depends entirely on trade size. Sandwiching a 0.1 SOL swap is not worth a searcher's effort; sandwiching a large swap on a thin pool very much is. For campaigns built from many small trades, the honest answer is that MEV exposure per trade is low and the tip is mainly buying execution reliability. For campaigns using large trades on illiquid pairs, the protection is the point. A vendor that recommends the same routing for both is not thinking about your cost.

More on the attack itself in sandwich MEV protection.

Why tips vary so much

A tip is an auction bid, not a price list. What you must pay is set by what other bundles are bidding for the same block, so tips rise sharply during launches, liquidations and any event that makes ordering valuable to many parties at once. There is no fixed figure anyone can quote honestly, which is why we publish the mechanism and the measured fee data separately rather than inventing a single number.

Practically, tips behave like a queue that reprices constantly. In quiet conditions a small tip wins inclusion. In contested conditions the same tip loses, the bundle does not land, and you retry. Because bundles are all-or-nothing, a losing bid produces no partial progress at all, which makes under-bidding on bundles worse than under-bidding on ordinary transactions.

This creates a real design decision for volume campaigns. Bundle everything and you pay tips on every batch, gaining reliability and MEV protection. Send ordinary transactions and you pay no tips but accept interception risk and less predictable ordering. Most sensible campaigns mix the two: bundle the trades where sequence matters, send the rest normally. Our measured per-program fee and failure data is on the measurement page; tips sit on top of those figures.

How to budget for tips

Estimate the number of bundles rather than the number of transactions, since a tip is charged per bundle. Divide your trade count by the transactions you can fit per bundle, multiply by the tip level appropriate to the conditions you expect, and treat the result as variable rather than fixed. Then add an allowance for bundles that lose their auction and have to be resubmitted.

A worked shape, without inventing a tip figure: 3,000 swaps batched at four per bundle is 750 bundles. Whatever tip level you plan for is multiplied by 750, and if a fifth of bundles lose their first auction you are paying for roughly 900. The tip level itself you should sample from current conditions rather than take from any page, including this one, because it was accurate for about a minute when written.

The pattern worth avoiding is budgeting tips as a percentage of volume. Tips scale with bundle count and competition, not with the size of your trades, so a campaign of many small swaps can pay more in tips than a campaign of few large ones at identical volume. Full campaign arithmetic is in the cost breakdown.

Because a tip is a bid rather than a price, it is excluded from every estimate on this site. What is included is set out on the pricing page and measured on the Solana volume bot overview.

Whether a tip is worth paying also depends on the venue. On a contested Pump.fun bonding curve, inclusion reliability is the scarce thing and a tip buys real protection against losing the race. On PumpSwap, a Raydium pool or Meteora DLMM, small trades against real depth are poor sandwich targets, so the tip is usually buying speed you do not need. Routing through Jupiter changes the calculation again, because larger multi-hop transactions fail more often before a tip ever matters.

Questions

Is a Jito tip the same as a Solana priority fee?

No. A priority fee bids for compute scheduling within Solana's normal transaction processing. A Jito tip bids for inclusion of an atomic bundle. They are separate payments with separate mechanics, and a campaign using bundles typically pays both.

What happens if my bundle does not win?

Nothing in it executes. Bundles are all-or-nothing, so a losing bid produces no partial progress and the transactions must be resubmitted. This makes under-bidding on bundles more costly than under-bidding on ordinary transactions.

Does bundling hide my volume bot activity?

No. Bundling controls execution ordering, not visibility. Every transaction remains on chain and readable. Coordinated wallet fleets stay identifiable through funding patterns and timing regardless of how transactions were submitted.

Do I always need Jito routing for a volume campaign?

Not always. Sandwiching small trades is rarely worth a searcher's effort, so for campaigns built from many small swaps the tip mainly buys execution reliability rather than meaningful MEV protection. For large trades on thin pools the protection is the main reason to route this way.

How much should I tip?

Sample current conditions rather than trusting a published figure. Tips are auction bids that reprice continuously, so any specific number in an article is stale almost immediately. What is stable is the mechanism: you are bidding per bundle against everyone else who wants that block ordering.

Sandwich MEV protection Solana priority fees Measured transaction costs Full cost breakdown