MEV — maximal extractable value — is profit extracted by reordering, inserting, or censoring transactions within a block. It's a fundamental property of blockchains where validators control transaction ordering. On Solana, it works differently than Ethereum but still affects every DeFi trader.
What MEV Actually Is
When you submit a swap transaction, it sits in the mempool (pending transaction pool) for a brief period before a validator includes it in a block. Anyone watching the mempool can see your pending transaction — including the amount, the tokens, and the expected price impact.
A bot (or validator) can:
Sandwich attack — Insert a buy before your transaction (pushing price up) and a sell after it (pushing price back down). You pay a worse price; the bot captures the difference.
Frontrunning — See your large buy order and execute a smaller buy first, then sell into your buy for profit.
Arbitrage — Not harmful to users. Bots close price discrepancies between DEX pools faster than humans can, keeping prices efficient.
Liquidation racing — When a lending position becomes undercollateralized, multiple bots race to liquidate it first and collect the liquidation bonus.
MEV on Solana vs. Ethereum
Ethereum has a transparent mempool — all pending transactions are visible to MEV searchers. Sandwich attacks are extremely common and well-documented.
Solana's architecture is different:
- No global mempool — Transactions are sent directly to validators, not broadcast to a public pool
- Faster blocks (400ms) — Less time for bots to react
- Jito's block engine — Jito Labs runs MEV infrastructure on Solana, routing bundles through validators running Jito's client
On Solana, MEV exists but is more structured. Jito's system allows for "priority fee" bundles — you pay extra to get your transaction processed first. This creates a more formalized MEV market compared to Ethereum's chaotic mempool sniping.
How It Affects Your Swaps
For most retail traders doing moderate-size swaps ($100–$10,000):
- MEV impact is typically small (less than 0.1% slippage from sandwiching)
- The bigger cost is usually price impact from pool depth, not MEV
- Higher slippage tolerance makes you a more attractive sandwich target
For larger swaps ($50,000+):
- Split into multiple transactions to reduce sandwich profitability
- Use DEX aggregators (like Jupiter) that route through multiple pools — harder to sandwich efficiently
- Use MEV-protected RPC endpoints (Jito's private mempool)
Jupiter's MEV Protection
Jupiter (which powers SovereignSwap) routes transactions through Jito's block engine with options for MEV protection. Transactions routed through private channels aren't visible to sandwich bots in the same way public mempool transactions are.
For large swaps, Jupiter's default routing already provides significant MEV protection by:
- Splitting trades across multiple pools (reduces each pool's price impact)
- Using Jito's infrastructure for private transaction routing
- Simulating optimal slippage before submission
jitoSOL and MEV Yield
MEV isn't purely a cost for users — it's also revenue for validators and their stakers. Jito's liquid staking token (jitoSOL) distributes MEV profits back to stakers, adding ~0.5–0.8% APY on top of standard staking rewards.
This means jitoSOL holders are partially compensated for the MEV that affects them as traders — a novel economic alignment.
Read the liquid staking guide →
Protecting Yourself
- Use aggregators — Jupiter and SovereignSwap already implement the best available routing and MEV protection
- Set tight slippage — 0.5% for liquid pairs. Don't set 5% "to make sure it goes through" — that's a sandwich invitation
- Split large trades — Multiple smaller transactions are harder to sandwich profitably
- Avoid thin markets — Low-liquidity tokens have higher price impact and more sandwich risk