Priority fees vs Jito tips on Solana: what each pays for

The short answer

A priority fee is Solana's own fee for scheduling: you set a price per compute unit, the runtime charges it on every transaction that lands, failed or not, and the whole amount goes to the block producer. A Jito tip is an ordinary SOL transfer, at least 1,000 lamports, to one of eight Jito tip accounts; it only counts when the leader is connected to Jito's block engine, and it is not paid if the transaction or bundle fails. On November 4, 2026, typical landed tips were a few thousand lamports, about 0.000003 SOL.

What is a priority fee?

A priority fee is an optional per-compute-unit price, set with the Compute Budget program's SetComputeUnitPrice instruction, that validators use to order transactions competing for the same accounts. It costs the price in micro-lamports times the compute unit limit, divided by 1,000,000. Since SIMD-0096, approved by validator vote in May 2024 and now live, 100% of the priority fee goes to the validator that produces the block; only the 5,000-lamport base fee is still half burned.

The formula, defaults and how to pick a number are covered in how much priority fee to pay on Solana, and the base fee and rent in Solana transaction fees explained. What matters for this comparison is that the priority fee is enforced by the protocol. Every validator's scheduler sees it, and once your transaction is in a block the fee is gone, whatever happens next.

What is a Jito tip?

A Jito tip is a plain SOL transfer to one of the eight tip accounts that Jito's block engine returns from getTipAccounts, used to bid for inclusion through Jito. Jito's low-latency transaction docs say the tip "can be any instruction, top-level or CPI, that transfers SOL to one of the 8 tip accounts", and that Jito enforces a minimum of 1,000 lamports for bundles.

As of November 2026, these are the tip accounts:

Jito tip accounts (mainnet)
96gYZGLnJYVFmbjzopPSU6QiEV5fGqZNyN9nmNhvrZU5
HFqU5x63VTqvQss8hp11i4wVV8bD44PvwucfZ2bU7gRe
Cw8CFyM9FkoMi7K7Crf6HNQqf4uEMzpKw6QNghXLvLkY
ADaUMid9yfUytqMBgopwjb2DTLSokTSzL1zt6iGPaS49
DfXygSm4jCyNCybVYYK6DwvWqjKee8pbDmJGcLWNDXjh
ADuUkR4vqLUMWXxW9gh6D6L8pMSawimctcNZ5pGwDcEt
DttWaMuVvTiduZRnguLF7jNxTgiMBZ1hyAumKUiL2KRL
3AVi9Tg9Uo68tJfuvoKvqKNWKkC5wPdSSdeBnizKZ6jT

The block engine runs auctions every 50 ms and ranks bundles by tip relative to the compute units they request. Tips collect in the tip accounts and are distributed at the end of each epoch to the validator that produced the block and its stakers, after Jito's protocol fee (3% according to Jito's JitoSOL technical FAQ) and the validator's own MEV commission.

A bundle is a group of up to five transactions that Jito executes in order and all-or-nothing. That atomicity is the main thing a tip buys that a priority fee cannot.

How do priority fees and Jito tips compare?

The two differ in who sees them, who gets paid, and above all what happens when a transaction fails:

	Priority fee	Jito tip
What it is	A protocol fee: compute unit price × compute unit limit	A SOL transfer instruction to a Jito tip account
How you set it	SetComputeUnitPrice and SetComputeUnitLimit (Compute Budget program)	SystemProgram.transfer to one of 8 tip accounts, in the same transaction or a bundle
Who receives it	100% to the leader that produced the block	The Jito-connected leader and its stakers, after Jito's protocol fee and the validator's commission
Which leaders honor it	Every validator	Only leaders connected to Jito's block engine; elsewhere it is just a transfer
When it is paid	Whenever the transaction lands in a block	Only if the transfer executes, so only on success
Cost of a failed transaction	Base fee plus the full priority fee	Nothing: the transfer is rolled back with the rest of the transaction
Cost of a bundle that does not land	Nothing for any transaction in it	Nothing
Minimum	None (zero is valid)	1,000 lamports
Typical size, November 4, 2026	0 network-wide; about 10,000 micro-lamports on the Raydium SOL-USDC pool, or 2,000 lamports for a 200,000-unit swap	About 2,500 lamports median in decoded transactions
How to see it on chain	Fee field minus base fee	A System transfer to a tip account

One caveat on "only paid on success": if you put the tip in its own transaction inside a bundle, that tip transaction can in rare cases be rebroadcast on its own and land without your trade. Jito warns about this "uncle bandit" risk and recommends putting the tip in the same transaction as the logic it pays for.

Why does a failed transaction cost a priority fee but not a tip?

Because the priority fee is charged by the runtime before execution, while a tip is just one of the instructions being executed. When a transaction fails, Solana reverts every state change the instructions made, including a SOL transfer to a tip account, but keeps the fee it already collected. Expired and never-landed transactions pay neither.

I saw this directly. Among the transactions I pulled from Jito's tip accounts on November 4, 2026, two had failed. Both had their tip transfer reverted, so the tip accounts received 0 lamports, and both still paid their priority fees of 6,800 and 929 lamports. The common errors behind failures like these are in why Solana transactions fail.

Bundles go a step further. If you send through Jito with bundleOnly=true, which Jito calls revert protection, a transaction that would fail is simply dropped and pays nothing at all, not even the base fee. That is why bots that fire many attempts at a launch prefer bundles: a missed attempt costs only the latency.

How much of Solana runs Jito?

Jito's tips only work on leaders connected to its block engine, and that is now a majority of stake but no longer nearly all of it. Jito's own Q2 2026 report, as summarized by Solana Compass on August 10, 2026, put the Jito client family, Jito-Solana plus its Block Assembly Marketplace (BAM), at about 54% of active stake at the end of June 2026, with BAM alone at 33%. The same report put Harmonic, a competing block builder, at roughly 21%.

Counts differ by method. Syndica's April 2026 on-chain report breaks stake down by scheduler and gives Agave Jito 36% and JitoBAM 28%, plus Jito variants of Frankendancer and Firedancer, a higher total. Either way, a tip-only transaction gets no help from roughly half of all leaders, which is why Jito recommends paying a priority fee too.

The tipping market has also spread beyond Jito. Syndica's March 2026 report found that non-Jito inclusion services captured 51% of tip volume, up from 22% in early 2025, with 0slot, bloXroute, Helius and others each running their own tip accounts. Helius Sender, for example, requires both a priority fee and a tip on every transaction, with a minimum of 0.001 SOL for its fastest tier, according to its documentation.

What were real priority fees and tips on November 4, 2026?

Both were small. Between 06:39 and 06:50 UTC on November 4, 2026, I sampled getRecentPrioritizationFees seven times (1,050 slots per account), read Jito's tip floor endpoint at https://bundles.jito.wtf/api/v1/bundles/tip_floor four times, and decoded the 15 most recent transactions touching each of the eight tip accounts.

Priority fees, per-slot minimums in micro-lamports per compute unit:

Accounts queried	25th percentile	Median	90th percentile	Highest
None (network-wide)	0	0	0	3,213
Raydium AMM v4 SOL-USDC pool	0	10,000	10,000	1,251,273
Orca Whirlpool SOL-USDC pool	0	0	835	254,069

Jito tips, in lamports:

Source	25th percentile	Median	75th percentile	95th percentile
Tip floor endpoint, 4 snapshots	1,000 to 5,313	1,141 to 13,814	5,000 to 20,000	17,261 to 80,000
62 successful transactions I decoded	1,024	2,500	10,000	30,000 (90th)

Two things stand out from the decoded sample. First, 47 of the 62 tip-paying transactions paid no priority fee at all, so many senders put the whole bid in the tip. Second, the minimum shows up constantly: 29 of the 62 tips were between 1,000 and 1,500 lamports. The largest was 275,584 lamports, about 0.00028 SOL.

Put in SOL, a median tip of 2,500 lamports is 0.0000025 SOL, and a 10,000 micro-lamport priority fee on a 200,000-unit swap is 0.000002 SOL. They are the same order of magnitude, and both are tiny next to the 0.01 SOL defaults some trading bots ship with, which is 4,000 times the median tip. These are ten minutes of data; the Priority Fee tracker shows the live fee market for any accounts you paste.

How do wallets and trading bots set each one?

Wallets set priority fees and leave tips alone, while trading bots usually expose both, calling the tip a "bribe". At the time of writing:

• Phantom adds a priority fee automatically to transactions that have no Compute Budget instructions of their own, according to its developer docs, and asks dApps not to set fees themselves. Those docs cover priority fees only, not tips.
• Jupiter's Swap API V2 /order endpoint takes a priorityFeeLamports value, chosen automatically if you leave it out, and a separate jitoTipLamports value. Its response field prioritizationFeeLamports "includes priority fees and tips (Jito, Nozomi)", per the API reference.
• BullX has separate Priority Fee and Bribe fields, each defaulting to 0.01 SOL, per its fees and gas docs. Its MEV Only Mode sends only through Jito, and the docs say the priority fee is then "less critical" because the bribe drives prioritization.
• Telegram bots such as Trojan and BONKbot offer similar fee and MEV-protection settings; check each bot's current menu, since they change often.

This is where the error people search for comes from. When a bot says your balance cannot cover the priority fee and bribe fee, the wallet does not have enough SOL for the trade plus both fees plus any bot fee. BlinkBot's common errors page, for example, describes its insufficient-funds error as not enough SOL "to cover transaction fees, tips (e.g., Jito Tips), and bot taxes". With 0.01 SOL defaults, a single buy needs 0.02 SOL in fees on top of the trade, and a new token account another 0.00148844 SOL of rent. Lowering both settings fixes it more often than topping up does. Bot wallets also pile up empty token accounts; reclaiming SOL from trading bot wallets covers getting that rent back.

Does a Jito tip protect against sandwich attacks?

Not on its own. What can help is how the transaction is sent, and the biggest factor is your slippage setting. Solana's MEV protection guide describes Jito's jitodontfront option: add any account whose address starts with jitodontfront as a read-only key, and the block engine will only accept bundles where your transaction comes first, so nobody can be placed before it. That only applies to transactions sent through Jito's block engine, and Jito says it is not guaranteed to stop sandwiches.

So "MEV protection" in a bot usually means three things: sending only to Jito-connected leaders, using bundle rules like revert protection and don't-front, and paying a tip to make that route fast. The tip is the price of the route, not the protection itself. Tight slippage, which the same guide calls the most effective defense, works on every route.

When should you use a priority fee, a tip or both?

Use a priority fee for almost everything, and add a tip only when you need Jito's bundle features or are racing other bots for the same block:

Situation	Priority fee	Jito tip	Why
SOL or token transfer	Small or wallet default	No	Nobody competes for your accounts
Ordinary swap in a wallet	Wallet or Jupiter auto	No	Auto priority fees land swaps on every leader
Wallet cleanup, closing accounts, staking	Small	No	No race; a tip buys nothing
Several transactions that must succeed together	Optional	Yes, in a bundle	Only bundles are all-or-nothing
Sniping a launch or arbitrage	Yes	Yes	You need both Jito and non-Jito leaders, and revert protection limits the cost of misses
Worried about sandwiches on a large swap	Yes	Optional, with don't-front	Tight slippage matters more than either fee
Sending through Helius Sender or similar	Required	Required	The service requires both

For a single urgent transaction, Jito's docs suggest splitting the budget about 70% priority fee and 30% tip. That keeps you competitive on the roughly half of leaders that do not run Jito's stack.

How do you check what you paid?

Paste the signature into the Transaction Decoder. It splits the network fee into the 5,000-lamport base fee and the priority fee, and shows compute units consumed next to the limit requested. A Jito tip is not part of the fee: it shows up as a System Program transfer instruction from your wallet to one of the eight addresses above, so look for it in the instruction list. If you are trying to explain a balance that keeps dropping, add up both, along with the other costs in why your Solana balance is lower than expected.

How does SOLTidy handle priority fees and tips?

I built SOLTidy to pay priority fees only, never Jito tips, because closing accounts or burning NFTs is not a race. Before each transaction it adds two Compute Budget instructions, unless the instructions already include them:

1. A compute unit limit from a simulation of the transaction: units consumed plus 20%, plus 1,000, capped at 1,400,000, or 300,000 if simulation fails.
2. A compute unit price from getRecentPrioritizationFees on the accounts the transaction writes to: the 75th percentile of recent non-zero fees, kept between 10,000 and 300,000 micro-lamports, or 50,000 if the lookup fails.

Swaps for selling dust tokens come from Jupiter with their own compute budget, set to Jupiter's medium priority level and capped at 50,000 lamports so the fee cannot eat a small sale. Because those instructions are already present, Phantom does not add its own fee on top. The wallet cleanup and the other tools that build their own transactions follow the same rules; the SOL wrap and unwrap tool leaves the priority fee to your wallet. None of them adds a Jito tip.

Bottom line

A priority fee and a Jito tip both buy faster inclusion, but they are different payments. The priority fee is a protocol fee that every validator honors and that you pay even when the transaction fails. A Jito tip is a SOL transfer of at least 1,000 lamports that only Jito-connected leaders, about 54% of stake in mid-2026, act on, and it is never paid if the transaction or bundle fails. For transfers, swaps and wallet cleanup, a small priority fee is enough. Add a tip when you need bundles, revert protection or a launch race, and keep it near the going rate, a few thousand lamports on November 4, 2026, rather than a bot's 0.01 SOL default. Check live numbers in the Priority Fee tracker and what you actually paid in the Transaction Decoder.