What exactly is MEV? MEV stands for "maximal extractable value," the extra profit that those with the power to decide "in what order this batch of transactions is arranged" — miners, validators, or searcher bots watching pending transactions — can extract before a Block is finalized and written on-chain, by reordering, inserting, or piggybacking their own transactions. Its root: transactions waiting to be processed on a blockchain are publicly visible before confirmation, and whoever can decide the ordering holds the power to manipulate. For ordinary users, MEV most often shows up as "your trade inexplicably filling at a worse price."
How exactly does a sandwich attack squeeze you? Imagine you're buying a coin on a DEX. Step one, you submit a buy order, and it enters the public pending area, where everyone (including attacker bots) can see you're "about to buy." Step two, the attacker's bot buys the same coin ahead of you, pushing the price up. Step three, your buy fills, but since the price is already pushed up, you buy at a worse price than expected. Step four, the attacker immediately sells what they just bought behind you, pocketing the spread created by their push and your taking it. Your trade is sandwiched between the attacker's "buy first" and "sell after," like the filling in a sandwich — hence the name, and the reason you inexplicably overpaid.
Why do I get targeted by sandwich attacks, and what kind of trades are most dangerous? Two root causes. First, publicity: on most public chains, the trade you submit enters a public pending area before confirmation, and attacker bots can scan in real time and see the trade you're about to make. Second, and the key you can control — Slippage tolerance. When you set slippage loose (allowing a large gap between fill price and the price you saw), you're proactively telling the attacker "I'll accept up to this price," so they can comfortably push the price to your tolerance ceiling before letting you fill. So the most dangerous trades are: large amounts (more juice to squeeze), shallow-liquidity pairs (price easily moved), and loose slippage (lots of room for the attacker). All three together is nearly inviting a bot to sandwich you.
How do I protect myself and minimize the squeeze risk? A few practical measures, simple to advanced. First, and simplest: set Slippage tolerance tight (within a reasonable range that still fills). The tighter the slippage, the less room the attacker has to move the price, and the less they can extract; but too tight and the trade may fail on minor price moves, so calibrate. Second, use a wallet, aggregator, or route supporting "private transactions" or built-in MEV protection, so your trade bypasses the public pending area, the attacker can't see it, and naturally can't sandwich it. Third, split large trades into batches to reduce the value exposed in a single one. Fourth, avoid extremely shallow-liquidity small-coin pairs as much as possible — they're the high-risk zone for sandwiching. Combine these and an ordinary user can actually push this risk quite low.
Swapping coins on a decentralized exchange (DEX), you may have hit something odd: the price looked fine when you placed the order, but after it filled, you found the price was noticeably worse than expected. Behind this, you were likely sliced by a sandwich attack, a form of "MEV." This piece clarifies what MEV is, how a sandwich attack works, and how you can protect yourself.
MEV (Maximal Extractable Value) refers to the extra profit that those able to decide transaction "ordering" (miners, validators, or specialized searcher bots) can extract before a Block is finalized, by adjusting transaction order and inserting their own transactions. Simply put, because pending transactions on-chain are publicly visible, someone can place orders ahead of or behind you, eating value that should have been yours.
A sandwich attack is the most common form of MEV. The flow: you submit a buy order on a DEX, and this transaction first enters the public "pending area" (Mempool). The attacker's bot sees it, buys ahead of you (pushing the price up), then your buy fills at the pushed-up price (you paid more), and then the attacker immediately sells behind you, pocketing the spread in between. Your trade is sandwiched between the attacker's "buy first" and "sell after," like the filling of a sandwich — hence the name.
Two key reasons. First, pending transactions on-chain are public, so bots can see in real time what you're about to do. Second, Slippage tolerance set too high: when you allow a large gap between fill price and expected price (high slippage), you've given the attacker room to push the price to your tolerance ceiling. The larger the trade amount, the shallower the liquidity, and the looser the slippage setting, the easier a target you are.
A few practical measures. First, set Slippage Tolerance low (within reason): the tighter the slippage, the less room the attacker has to extract, though too tight may cause the trade to fail, so calibrate. Second, use tools or routes supporting "private transactions / MEV protection" so your trade doesn't pass through the public pending area, and the attacker can't see or sandwich it. Third, consider splitting large trades into batches to reduce the value locked in a single one. Fourth, avoid trading pairs with extremely shallow liquidity, where it's easiest to be sandwiched.
MEV is a structural byproduct of public, orderable blockchains and won't fully disappear soon, but you needn't fear using a DEX because of it. For ordinary small trades, the impact is usually limited; what to truly watch are large, low-liquidity trades with very loose slippage. Understand the principle, set slippage well, and use MEV-protection tools, and you can push the squeeze risk down to an acceptable level.