Axiom Blog

Solana priority fee vs Jito tip

A priority fee is an optional fee paid through Solana itself that increases a transaction's scheduling priority with the validator. A Jito tip is a separate SOL payment used with Jito's block engine, and it goes to validators that run Jito's software and their stakers. Both relate to getting a transaction into a block. Neither one guarantees that it gets in, how fast it confirms, or what price you get.

The useful distinction is between ordering and outcome. Both payments are bids for a place in line. Where a trade lands in that order can affect the pool state it meets, and so the price it gets. But neither payment sets the price directly or overrides the conditions the trade must meet when it runs.

The priority fee

Every Solana transaction pays a base fee and can add an optional prioritization fee. Solana's docs say the prioritization fee increases the scheduling priority of a transaction and that all of it goes to the validator. Source: Solana's fee structure docs

Solana's docs describe the priority fee as a compute unit price multiplied by the compute unit limit the transaction requests, and say the fee is based on the requested limit, not on what the transaction actually uses. They also describe the scheduler ranking transactions by the validator's reward relative to the transaction's estimated cost. Source: Solana's fee structure docs. The implication is that priority is relative. The same fee can rank differently depending on what else is competing at that moment and how expensive the transaction is to run.

Solana's docs also say the fee is deducted before execution begins and is still charged if the transaction fails. That applies to a transaction a validator processes that then fails during execution. It does not describe a trade an app refuses before sending it, or a transaction that is dropped and never processed. Source: Solana's fee structure docs

The Jito tip

Jito runs a block engine that validators running its Jito-Solana client connect to. Jito's docs say a tip is necessary for a bundle to be considered, and describe the tip as a transfer of SOL to one of Jito's tip accounts, with tips redistributed to validators and their stakers. Jito's docs say a tip that is too low might not be selected in its auction, and that tips do not prioritize transactions when the current leader is not running Jito-Solana. Source: Jito's low latency transaction send docs

The tip is its own transfer, so the Solana fee rules above do not describe when a tip is charged.

Jito's docs describe bundles as groups of transactions that run in order and all-or-nothing within one slot. They say bundles whose account locking patterns intersect, meaning at least one writes to an account the other reads or writes, run in a single auction. Bundles that don't touch the same accounts, or only read the same accounts, run in separate auctions. Within an auction, bundles are ordered by tip relative to the compute they request. Source: Jito's low latency transaction send docs. The implication is that a tip is compared first with bundles in the same auction, not with every transaction on the network.

Jito's docs also note a limit on that all-or-nothing behavior. If bundle transactions end up in a block the network skips and someone rebroadcasts them, they can be processed as ordinary transactions without the bundle's protections. Source: Jito's low latency transaction send docs

Jito also offers a feature against some kinds of front running, and its docs say it may help but is not guaranteed. Source: Jito's low latency transaction send docs

How they relate

They are two separate payments on two different paths. The priority fee works through Solana's normal scheduling. The tip works through Jito's auction. For its single transaction send method, Jito's docs suggest setting both. Source: Jito's low latency transaction send docs

What a higher fee or tip can and cannot change

The tradeoff runs both ways, and when you pay depends on the path. Solana's fee docs say the base and priority fees are deducted from the fee payer before execution begins and are charged even if the transaction fails. Source: Solana's fee structure docs. Solana's confirmation guide says a transaction whose recent blockhash has expired is not processed. Source: Solana's transaction confirmation guide. Our reasoning from those two points, not a quote from either source, is that a transaction dropped or expired before processing never reaches the deduction step and so doesn't pay those network fees. For bundles, Jito's docs say that if the tip instruction is in the same transaction as the trade, and that transaction fails, the tip isn't paid. That describes one arrangement, not every way a tip can be sent. Jito's docs advise caution with sending the tip as a standalone transaction in a bundle, saying it may increase exposure to rebroadcast scenarios. They also warn that rebroadcasts after skipped blocks are an exception to bundle protections. Source: Jito's low latency transaction send docs. So a higher bid costs more whenever the transaction is processed or the tip lands, without a matching guarantee of better ordering or a better result. A lower bid costs less in those same cases, but it can leave a time-sensitive trade behind competing transactions while the state changes or the blockhash expires, and it doesn't make a processed failure free. Neither setting is correct in every condition. Neither payment guarantees inclusion.

How this looks in Axiom

Axiom's Solana trading settings have a separate BRIBE field next to PRIORITY, and the bribe is tied to the MEV Mode setting. Where a tip goes depends on how a transaction is sent. So a bribe in Axiom should not be read as always being a Jito tip. Axiom's docs also say that even a higher bribe is not 100% effective. Source: Axiom's Solana fees docs

Fees are not slippage

Slippage is the difference between the expected price of a trade and the price it actually executes at. A slippage tolerance is how much of that difference you permit before the trade is cancelled. A trade can fail because the price moved past your tolerance, whatever your priority fee or tip. Source: Axiom's Solana fees docs

Slippage is also different from price impact, which is how much your own trade moves the price.

These settings pull against each other. A wider tolerance permits more adverse price movement before the trade is rejected. It doesn't make the fill worse by itself, but it allows a worse fill if conditions move that way. Axiom's docs connect low slippage with less exposure to sandwiching when MEV protection is off. Source: Axiom's Solana fees docs. A tighter tolerance limits how far the price can move against you, but it makes a rejection more likely when the price does move. If that rejection happens in a transaction that was processed, Solana's fees are still charged. A trade an app refuses before sending, or a transaction that is dropped, is a different case. Source: Solana's fee structure docs.

If a trade failed with an insufficient SOL message, see why Axiom says insufficient SOL balance to cover priority fee and bribe fee.

Crypto trading is high risk and you can lose everything you put in. Nothing here is financial advice.