MEV, Sandwich Attacks and Jito Explained for Solana Traders

Updated 2026-10-11 | 4 min read | QUANTUM (QNT) community

What MEV means

MEV stands for maximal extractable value. Solana's own guide describes it as value captured by reordering, including or excluding transactions within a block. Some MEV is harmless or even useful: arbitrage helps keep prices consistent across markets. The harmful kind is where someone profits directly at a trader's expense. To see where it happens, read how Solana transactions work first.

How a sandwich attack works

A searcher is a person or bot hunting for these opportunities. In a sandwich attack:

1. Your swap is pending, and you have allowed a certain slippage.
2. The searcher buys the same token first. This pushes the price up.
3. Your trade executes at the worse price.
4. The searcher sells right after, at the higher price, and keeps the difference.

Your extra cost is roughly the attacker's gain plus fees. Thin pools make it worse, because even a small buy moves the price. This links directly to liquidity depth and price impact and to slippage and priority fees.

Where Jito comes in

Jito runs a Block Engine and a modified validator client, called Jito-Solana, that many validators use. Per Jito's documentation, a bundle is a group of up to 5 transactions that execute in order and all-or-nothing within the same slot. Bundles carry tips, which are paid to one of 8 designated tip accounts and redistributed to validators and their stakers, with a minimum tip of 1000 lamports. Bundles compete in auctions that run in 50 millisecond ticks.

That machinery is neutral. Atomic arbitrage uses it for good, and a sandwich attacker can use it to make sure the front-run, your trade and the back-run land together. Solana's guide says exactly that: on Solana this can occur through Jito bundles ordering transactions as front-run, victim and back-run.

Why Solana is different from Ethereum

Solana has no public mempool in the usual sense. Per Solana's guide, transactions go directly to the upcoming block leader, and unprocessed transactions expire after about 150 blocks, roughly one minute. That reduces exposure, but does not remove it. A July 2024 Blockworks Lightspeed newsletter reported that sandwich attacks were still happening and that the ones being tracked were mostly memecoin swaps, which hits newer retail traders. A later Blockworks piece quotes Anza economist Max Resnick saying the rate was "way down" after code improvements. Current levels may differ, so treat any single number you read as a snapshot.

What you can do

• Set tight slippage. Solana's guide calls this the most effective transaction-level defense. If the price moves beyond your limit, your swap fails instead of filling badly. On thin memecoins a very tight limit may cause failed swaps, and a very loose one invites sandwiches. Find a balance. See the slippage guide.
• Use protected submission where offered. Jito's sendTransaction applies MEV protection by default, and its docs say setting bundleOnly to true adds revert protection. Many wallets and swap tools enable some protection for you. Look in your settings, and see the Jupiter guide.
• Know about jitodontfront. Developers can add a special read-only account starting with jitodontfront to a transaction, so the Block Engine only accepts bundles where that transaction is first. Jito's own wording: it "may help reduce sandwich attacks but is not guaranteed to do so." It only applies where the app or wallet adds it.
• Prefer deeper pools and smaller trades. Splitting an order or trading in a pool with more liquidity gives an attacker less to push.
• Consider limit orders where available. They avoid the same kind of exposure, though they may not fill on fast markets.

Tips versus priority fees

You may see two ways to pay for speed. A priority fee goes into the normal fee system. A Jito tip is a separate payment aimed at validators running the Block Engine. For sendTransaction Jito's docs recommend splitting fees roughly 70 percent priority fee and 30 percent tip. Higher tips do not make a bad trade a good one: they only change how fast it lands.

Spotting a sandwich after the fact

If a swap filled far worse than the quote, open the transaction in Solscan and look at the transactions directly before and after yours in the same block. Two trades by the same wallet around yours, one buy and one sell, is the pattern. Learn to read it with the transaction guide. You usually cannot get the money back, so prevention matters more.

Keep it in proportion

MEV is one cost of trading, like fees and price impact. It is not the same as a scam, though it can feel like one. Combine protections with risk management and the guidance in setting a budget. This is education only, not financial advice, and QNT is independent of Quantinuum Ltd.

Sources and further reading

• Solana: MEV Protection with Jito DontFront
• Jito docs: low latency transaction send
• Blockworks: Lightspeed newsletter on Solana sandwich attacks (July 2024)
• Blockworks: Solana sandwich attacks way down

Reported as of 2026-10-09. Rules, prices and tools change, so check the original pages.

Frequently asked questions

Share on X

Keep reading

• Slippage and Priority Fees on Solana Explained
  Slippage is the gap between the price you expect and the price you get. Priority fees pay for faster processing. Learn how to set both when swapping on Solana.
• How to Swap Tokens on Jupiter (Solana DEX Aggregator)
  Jupiter finds the best route to swap Solana tokens. Learn how to swap SOL for a token like QNT safely, with slippage explained.
• Liquidity Depth and Price Impact Explained: Why Trade Size Moves Price
  Learn how liquidity depth and price impact work in a pool, why larger trades move price more, and what the constant product idea means for memecoin traders.
• How Solana Transactions Work
  A clear look at how a Solana transaction is built, signed, sent and confirmed, including instructions, accounts, the recent blockhash and what finality means.

All How to buy and stay safe guides | Back to top | Search the site

Main pages: What is QNT? | Token information | How to buy | FAQ