In 2025 alone, 1.55 million sandwich attacks extracted roughly $13.43 million from Solana traders, hitting over 49,000 victims. That’s not a rare, isolated incident either, it’s a systemic, ongoing pattern with real, quantified victims, most of whom likely had no idea the setting they clicked past was directly enabling it. Most of that money was lost through a setting most people set once and never think about again: slippage tolerance. Understanding what it actually protects against, and what it doesn’t, matters more than most DEX tutorials let on. Understanding what is slippage in crypto, and why it gets exploited, is the first defense.
What Is Slippage in Crypto, Actually?
What Is a Decentralized Exchange (DEX)? covers how AMM pricing works; slippage is the gap between the price you were quoted and the price your trade actually executes at. This gap exists on every DEX trade to some degree, the only question is how large, and whether the setting protecting you against it is actually configured to help rather than quietly work against you. Slippage tolerance is the setting that caps how large that gap is allowed to be before your transaction reverts instead of executing at a worse rate.
Why It Happens: Two Different Causes
Price impact comes from your own trade size relative to the pool, a larger trade moves the pool’s ratio more, producing a worse average price on the same transaction. Time-based slippage comes from the price simply moving between when you got your quote and when your transaction actually confirms, especially during high volatility or network congestion. Both causes produce the same visible symptom, receiving less than your original quote, but they call for different responses: price impact is addressed by trading in smaller sizes or finding deeper liquidity, while time-based slippage is addressed by acting during calmer network conditions or accepting a tighter execution window.
A Concrete Example
You’re quoted 1,000 tokens for your trade. With 0.5% slippage tolerance, your transaction reverts entirely if the actual execution would give you fewer than 995. This is a protection, not a guarantee, it sets a floor, but anything above that floor and below your quote can still execute. Scale this to a larger trade and the mechanics stay identical, only the absolute numbers change, which is exactly why understanding the principle matters more than memorizing any specific percentage.
The Real Reason High Slippage Tolerance Is Dangerous
Your slippage tolerance is effectively a public statement of the worst price you’ll accept, visible to anyone watching pending transactions. This is worth sitting with for a moment, since it inverts the intuitive assumption most beginners make: slippage tolerance feels like a safety setting, and it partially is, but a loosely set one actively creates the opening a sandwich attack needs to be profitable in the first place. Set it to 5% because a trade kept failing, and you’ve told every bot monitoring the network exactly how much room a sandwich attack has to work with: a bot buys just ahead of your trade, pushing the price up, then sells immediately after yours executes, pocketing the difference your wide tolerance allowed. Tighten that same trade to 0.3%, and the same attack has far less room to be profitable, often not enough to cover the bot’s own gas cost at all.
| Slippage Setting | Risk Profile |
|---|---|
| Too low (near 0%) | Transaction frequently fails, especially on volatile pairs |
| Moderate (0.1%-0.5%) | Reasonable balance for most liquid pairs |
| High (2%+) | Executes more reliably, but creates real sandwich-attack exposure |
How to Actually Set Slippage Tolerance
For deep, liquid pairs like major stablecoin or blue-chip token swaps, 0.1% to 0.3% is generally appropriate. Less liquid or more volatile pairs sometimes genuinely need a higher setting to execute at all, but raise it deliberately and specifically for that trade, not as a permanent default you stop thinking about. Resist the instinct to simply raise slippage whenever a transaction fails without first understanding why it failed; a failed transaction due to genuine volatility calls for a different response than one failing because of thin liquidity in an obscure pool.
Managing slippage protects individual trades. Building a complete trading approach is the bigger picture.
The Crypto/DeFi Trading Course covers execution quality as part of a full, practical trading framework.
Other Ways to Reduce Your Exposure
Some wallets and RPC providers route transactions privately, away from the public pending-transaction pool bots monitor, closing off sandwich attacks at the source rather than just limiting their profitability. Checking whether your wallet or a specific DEX’s default RPC already includes some form of MEV protection is worth doing once, rather than assuming you’re automatically covered without checking. Intent-based DEXs, where solvers compete to fill your order rather than broadcasting it directly, offer a structurally different, often better-protected alternative worth knowing about for larger trades specifically. DEX vs CEX Fees: Which Actually Costs You More? covers how slippage factors into the broader real cost of trading on a DEX compared to a centralized alternative.
Preguntas frecuentes
Does tight slippage guarantee I won’t get sandwiched?
It significantly reduces the profitability of the attack, but doesn’t eliminate the underlying mechanism entirely. Combining tight slippage with private transaction routing offers meaningfully stronger protection.
Is a failed transaction from low slippage a bad outcome?
Generally not, a reverted transaction typically costs a small amount of gas but keeps your tokens safe, a far better outcome than executing at a manipulated price.
Why does slippage tend to increase during high market volatility?
Prices are moving faster during volatile periods, widening the gap between a quote and actual execution, and pools also tend to see more trading activity, compounding both causes of slippage at once.
Do all DEXs default to the same slippage setting?
No, defaults vary by platform, commonly somewhere around 0.5%, but always worth checking and adjusting for the specific pair and trade you’re actually making rather than assuming the default fits every situation.
Are sandwich attacks illegal?
Legally ambiguous in most jurisdictions currently. Technically, nothing is hacked or stolen in the traditional sense, a bot is using publicly broadcast information, which is part of why this remains a persistent, largely unresolved issue.
Does slippage affect small trades the same way it affects large ones?
Small trades on liquid pairs are rarely worth a bot’s attention, since gas costs can exceed the extractable profit. Larger trades and thinner liquidity are where slippage and MEV risk both matter most.
Slippage tolerance isn’t just a technical setting to click past, it’s a real trade-off between execution reliability and exposure to a genuine, quantified, ongoing threat. Setting it deliberately, tight by default, wider only when a specific trade actually requires it, is worth the extra few seconds of thought every single time. Knowing what is slippage in crypto swaps, and setting your tolerance deliberately, protects every trade you make.
Ready to trade with real execution discipline? The Crypto/DeFi Trading Course helps you build exactly that habit.
¿Prefieres aprender con un libro, a tu propio ritmo? La serie de libros sobre criptomonedas profundiza en este tema. Si eres nuevo en el mundo de las criptomonedas, empieza con el Libro 1 y luego continúa con la serie a tu ritmo.
Not sure what slippage setting makes sense for a specific trade? Join DavitoFinance Pro on Telegram, free, and ask before you confirm.
