Slippage in cryptocurrency trading refers to the difference between the expected price of a trade and the actual executed price. It occurs because market prices can change between the time a trade order is submitted and when it is confirmed, a particularly common phenomenon in volatile cryptocurrency markets and on automated market maker (AMM) DEXs.
On AMMs like Uniswap, slippage occurs because every trade moves the price along the bonding curve: larger trades in shallower liquidity pools cause greater price impact and thus more slippage.
Slippage tolerance settings allow traders to specify the maximum acceptable deviation from the expected price before a transaction reverts, balancing trade execution certainty against price precision.
Origin & History
| Date | Event |
|---|---|
| Pre-crypto | Slippage concept exists in traditional markets; bid-ask spread and market impact |
| Nov 2, 2018 | Uniswap V1 launches at Devcon 4; constant product AMM introduces DEX-specific price impact slippage |
| Jun 2019 | 1inch launches, introducing DEX aggregation and multi-pool routing to minimize slippage |
| May 2020 | Uniswap V2 launches with direct ERC-20 to ERC-20 swaps; slippage tolerance becomes a standard UI feature across DEX interfaces |
| 2020 | DeFi Summer: high mempool congestion increases realized slippage on DEX trades |
| 2020 | Sandwich attack bots emerge, exploiting high slippage tolerance settings to extract MEV |
| May 2021 | Uniswap V3 introduces concentrated liquidity; significantly reduces slippage within active price ranges |
| 2021 | DEX aggregators (1inch, Paraswap) refine optimal routing algorithms for large trades |
How It Works
AMM Price Impact (Uniswap Constant Product Formula: x * y = k)
Example pool: 1,000 ETH and 2,000,000 USDC, giving k = 2,000,000,000.
Small trade (buy 1 ETH): New ETH in pool: 999. New USDC required: 2,000,000,000 / 999 = 2,002,002. Cost: $2,002. Expected price: $2,000. Slippage: 0.1%.
Large trade (buy 100 ETH): New ETH in pool: 900. New USDC required: 2,000,000,000 / 900 = 2,222,222. Cost: $222,222. Expected price: $200,000. Slippage: 11.1%.
Slippage Tolerance Settings:
| Setting | Use Case |
|---|---|
| 0.1% | Very tight; may fail in volatile markets |
| 0.5% | Standard for major tokens |
| 1-2% | Common for mid-cap tokens |
| 3-5% | High; sandwich attack risk increases significantly |
| Above 5% | Very high risk of sandwich attack |
Trade Size vs. Pool Slippage:
| Trade Size (% of Pool) | Approximate Slippage |
|---|---|
| 0.01% | ~0.01% |
| 0.1% | ~0.1% |
| 1% | ~1% |
| 10% | ~10% |
| 50% | ~50% |
In Simple Terms
Moving the market price: Every buy order on an AMM pushes the price up slightly; every sell order pushes it down. Buying a small amount moves the price barely; buying 10% of available liquidity moves it significantly.
Smaller pool means bigger slippage: A $1M ETH trade on Uniswap’s deep ETH pool creates almost no slippage. The same $1M trade on a small new token with a $100K pool would make the token far more expensive by the end of the transaction.
Slippage tolerance as a safety net: When you set 1% slippage tolerance, you are telling the contract to cancel the transaction if the final price deviates more than 1% from the expected price. This protects you from unexpected price movements.
Sandwich attack risk from high tolerance: If you set 3% or more slippage tolerance, sandwich bots can profitably move the price just below that threshold before your trade, extract that value, and still have your transaction execute within tolerance.
DEX aggregators minimize slippage: Protocols like 1inch route large trades across multiple liquidity pools, reducing the impact on any single pool and achieving better average prices.
Real-World Examples
| Scenario | Implementation | Outcome |
|---|---|---|
| Large SHIB buy | User buys $10,000 of SHIB in a small liquidity pool | Expected 1M SHIB; receives 870,000 SHIB; 13% slippage |
| Tight slippage protection | User sets 0.1% tolerance in a volatile market | Transaction reverts; user pays gas fee but does not overpay for tokens |
| Sandwich enabled by high slippage | User sets 5% slippage; bot sandwich extracts 4% | User gets tokens but pays significantly more than expected |
| Aggregator routing | 1inch routes $100K ETH swap across 5 pools | Achieves 0.15% slippage vs. 0.8% on a single-pool route |
Advantages
| Advantage | Description |
|---|---|
| Slippage tolerance prevents catastrophic overpayment | Transaction reverts rather than executing at terrible prices |
| Price impact visible pre-trade | DEX interfaces show estimated price impact before confirming |
| Liquidity depth metric | Slippage serves as a proxy for pool liquidity health |
Disadvantages & Risks
| Disadvantage | Description |
|---|---|
| High slippage enables sandwich attacks | Wide tolerance makes MEV extraction more profitable |
| Tight tolerance causes failed transactions | Very low tolerance frequently reverts in volatile conditions |
| Gas cost on revert | Failed transactions due to slippage still cost gas fees |
| New token high slippage | Freshly launched tokens with low liquidity often require 3-10%+ slippage tolerance |
Risk Management Tips:
- Start with 0.5% slippage for established tokens; increase only if the transaction consistently fails
- Never set more than 1% slippage without MEV protection (Flashbots, MEV Blocker) active
- Check estimated slippage on the DEX interface before confirming; high slippage is a warning sign
- Split large trades into multiple smaller transactions to reduce pool price impact
- For new or low-cap tokens, use DEX aggregators that route across multiple pools
FAQ
Q: What is the difference between slippage and price impact?
A: Price impact is the percentage change in pool price caused by your trade, determined by trade size relative to liquidity. Slippage tolerance is your maximum acceptable deviation from the quoted price. Price impact is a physical market effect; slippage tolerance is a parameter you control.
Q: Why did my transaction fail with “slippage exceeded”?
A: Between the time you submitted the transaction and when it was included in a block, the price moved more than your slippage tolerance allowed. The contract automatically reverted to protect you from overpaying. You still pay gas fees for the failed attempt.
Q: What slippage should I set for low-liquidity tokens?
A: Low-liquidity tokens often require 3-10% slippage tolerance. However, this creates significant sandwich attack risk. If using high slippage, route through MEV protection (Flashbots Protect, MEV Blocker) to prevent bots from exploiting your tolerance setting.
Q: Do CEX trades (Binance, Coinbase) have slippage?
A: CEX trades use order books rather than AMMs. Market orders can experience slippage if the order book is thin, as you may fill at multiple price levels as you consume sell orders. Limit orders eliminate this by specifying an exact price.
Q: How do DEX aggregators reduce slippage?
A: Aggregators split large trades across multiple liquidity pools. Instead of buying $1M of ETH from one pool (high slippage), they route portions through several different pools (lower per-pool impact). The combined average price is better than any single pool could provide.
Related Terms
AMM (Automated Market Maker), Price Impact, Slippage Tolerance, Liquidity, Sandwich Attack, DEX Aggregator
UPay Tip: For tokens on Ethereum with decent liquidity, 0.5% slippage is almost always sufficient. If a transaction fails at 0.5%, the market is too volatile for the trade to be prudent anyway. For new or small-cap tokens where 3% or more is required, make sure MEV protection is enabled, or you are effectively donating that percentage to sandwich bots.
Disclaimer: This content is for educational purposes only and does not constitute financial advice. Always conduct your own research before making investment decisions.
