What Does High Slippage Tolerance Expose You To?
Raising slippage tolerance fixes failed transactions — and directly widens how much a sandwich attack can extract from you. Here's the trade-off.
Slippage tolerance is one of those settings people bump up once, out of frustration with a failed transaction, and then forget about entirely. What that setting actually controls is worth understanding, because it directly shapes how much risk every future trade carries.
What Slippage Tolerance Actually Sets
Slippage tolerance defines the maximum difference you're willing to accept between the price you saw when submitting a trade and the price it actually executes at. If the price moves beyond that tolerance before your transaction confirms, the transaction fails instead of executing at a worse price.
Why This Setting Exists at All
Prices on a liquidity pool can shift between the moment you submit a trade and the moment it's actually processed — other trades can execute first, changing the pool's ratio. Slippage tolerance is the safety margin that decides whether your trade should still go through despite that shift, or fail rather than accept it.
Why People Raise It in the First Place
A transaction failing due to slippage is a common frustration, especially on volatile or low-liquidity tokens — the default or a conservative setting can cause frequent failures, pushing people to raise the tolerance simply to get a trade to go through at all.
What a High Tolerance Actually Permits
Setting a high slippage tolerance — 10%, 20%, or more — tells your wallet to accept a trade even if the price has moved dramatically against you by the time it executes. The transaction will go through almost regardless of how unfavorable the final price turns out to be.
Why This Directly Increases Exposure to MEV Extraction
A high slippage tolerance is exactly what a sandwich attack needs to be profitable — it defines the ceiling for how much an attacker can push the price against you before your transaction would otherwise fail. A wide tolerance gives a bot far more room to extract value from your trade specifically.
Why This Matters More on Low-Liquidity Tokens
On a thin pool, prices are already easier to move — combining that with a high slippage tolerance compounds the risk considerably, since both factors independently increase how much a single trade's execution price can deviate from what you expected.
What a More Deliberate Approach Looks Like
Rather than raising slippage tolerance to a high, blanket setting to avoid failed transactions generally, adjusting it closer to what a specific trade actually needs — checking the pool's depth first, and accepting that some trades on very thin pools may need to be smaller or delayed rather than pushed through with an unreasonably wide tolerance.
Check a token's liquidity depth before setting a high slippage tolerance to force a trade through — the setting that fixes a failed transaction is the same one that widens your exposure to MEV extraction.