KoinlyticsEvery DEX trade goes through a public queue before it settles. That queue (the mempool) is visible to sophisticated bots that spend millions on hardware to see your transaction one microsecond before the validator does. In that microsecond they can insert their own transactions to extract value from yours. Welcome to MEV.
The three main flavors
Arbitrage
ETH is trading at $4,000 on Uniswap and $4,010 on Curve. A bot buys on Uniswap, sells on Curve, pockets the $10. Arbitrage aligns prices across venues. It is mostly benign — someone has to do it.
Sandwich attacks
You submit a $10,000 ETH → USDC swap. A bot sees it, front-runs by buying USDC first (pushing the price up), lets your swap execute at the worse price, then sells USDC back at profit. You paid more because the bot saw your transaction. This is the harmful kind.
Liquidations
A leveraged position on Aave becomes underwater. First bot to send the liquidation transaction wins the liquidation bonus. Not directly a tax on you unless you were the liquidated party.
The scale
Since the Ethereum Merge in Sep 2022, over $700M of MEV has been extracted on Ethereum alone. Real MEV volume is probably 2-3x higher when you include private mempool flow. Every sophisticated venue leaks value to bots one way or another.
How to defend yourself
1. Tight slippage
Slippage cap = maximum price movement you tolerate. Default 1% is generous. Set to 0.5% or lower for stablecoin pairs and 0.3% for well-liquid tokens. Anything above 1% is basically inviting sandwiches.
2. Private mempool
Route your transaction through a private mempool that hides it from bots until it is included. Options:
- Flashbots Protect — direct RPC endpoint, free
- MEV Blocker — free RPC by CoW Swap and Beaver Build
- CoW Swap — DEX aggregator that batches trades so sandwiches are unprofitable
3. Choose the right chain
Solana has different MEV dynamics (Jito auctions block space transparently, less sandwich-friendly). L2s vary wildly. Arbitrum has less MEV than Ethereum L1 today.
The uncomfortable truth
MEV is not a bug that will be fixed. It is a consequence of running a public, permissionless transaction queue. What can change is who captures the value: validators, bots, users, or the protocol. That is the ongoing arms race between users, block builders, and MEV searchers.
What to remember
If you swap on-chain without any MEV protection, you are paying an invisible tax. Set tight slippage. Use a private mempool. Consider Solana or an L2 for smaller trades. The tax is real. The defenses are free.