Slippage

What Is Slippage?

Slippage is the difference between the expected price of a trade and the actual price at which it executes. If you submit a swap expecting to receive 100 USDC per ETH but the trade fills at 98.5 USDC per ETH, you experienced 1.5% slippage. It is not a fee charged by an exchange: it is a natural consequence of how markets move between the moment you submit a trade and the moment it settles.

Slippage affects every trading venue, from centralized order books to on-chain automated market makers. However, the causes and severity differ. On centralized exchanges with deep order books, slippage on major pairs is often below 0.1% for trades under $100,000. On DEXs using AMM pools, slippage is deterministic and can reach double digits on low-liquidity pairs.

A related but distinct concept is price impact: the portion of slippage caused solely by your own trade moving the pool's price. External factors like other traders' activity, MEV bots, and market volatility account for the rest.

How It Works

The mechanics of slippage depend on the venue. On a centralized exchange, a large market order "walks the book," filling at progressively worse price levels as it consumes available liquidity. On an AMM-based DEX, slippage emerges directly from the bonding curve formula that governs the pool.

AMM Slippage and the Constant Product Formula

Most AMMs use a variant of the constant product formula: x × y = k, where x and y are the reserves of two tokens and k is a constant that can only increase. Every swap changes the ratio of reserves while preserving the invariant, and the further you push the ratio, the worse your effective price becomes.

Pool: 100 ETH × 100,000 USDC = 10,000,000 (k)
Spot price: 1 ETH = 1,000 USDC

Trader swaps 10 ETH into the pool:
  New ETH reserve: 110
  New USDC reserve: 10,000,000 / 110 = 90,909 USDC
  USDC received: 100,000 - 90,909 = 9,091 USDC

Expected at spot price: 10,000 USDC
Actual received: 9,091 USDC
Slippage: ~9.1%

The relationship is nonlinear: small trades produce negligible slippage while large trades relative to pool size produce exponentially worse execution. A 1 ETH swap on the same pool would yield approximately 990 USDC (about 1% slippage), while a 50 ETH swap would yield only 33,333 USDC (about 33% slippage).

Four Causes of Slippage

1. Thin liquidity: fewer tokens in the pool (or fewer orders on the book) means each trade moves the price further
2. Large order size: bigger trades consume more of the available liquidity, pushing the price further along the curve
3. Price volatility: rapid market movement between order submission and execution shifts the baseline price
4. Block delay: on-chain transactions wait for block inclusion, creating a window where the pool state can change from other trades or MEV activity

Positive vs. Negative Slippage

Slippage can work in your favor. Negative slippage (the common case) means you receive fewer tokens than expected. Positive slippage means market movement between submission and execution resulted in a better price than quoted. DEX aggregators like 1inch and Jupiter actively route trades across multiple pools to find price improvement opportunities.

Slippage Tolerance Settings

DEXs let users set a slippage tolerance: the maximum acceptable deviation from the quoted price. If the actual execution price would exceed this threshold, the smart contract reverts the transaction. You keep your original tokens but lose the gas fee spent on the failed transaction.

Uniswap's web app auto-sets tolerance between 0.1% and 5% based on swap size and network conditions. Setting tolerance too low causes frequent transaction reverts and wasted gas. Setting it too high opens the door to front-running and sandwich attacks.

Slippage and MEV

The relationship between slippage tolerance and maximal extractable value (MEV) is direct: your slippage setting defines the profit ceiling for attackers. A sandwich attack works by placing a buy order before your transaction (front-run) and a sell order after (back-run), capturing the spread your slippage tolerance permits.

The attack sequence:

1. A bot detects your pending swap in the mempool
2. It submits a buy for the same token with higher gas, ensuring its transaction lands first
3. The bot's purchase pushes the price up
4. Your swap executes at the inflated price (within your slippage tolerance)
5. The bot immediately sells into the price impact you created, pocketing the difference

Research from 2025 found that approximately 1.2% of all DEX trades on Ethereum are sandwiched, with an average loss of 0.41% of trade value per affected swap. Across Solana, sandwich bots extracted between $370 million and $500 million over a 16-month period. Tight slippage settings (0.1% to 0.3%) make sandwich attacks unprofitable because the extractable value falls below the attacker's gas costs.

MEV Protection Tools

Several tools reduce MEV exposure by bypassing the public mempool:

• Flashbots Protect sends transactions directly to block builders, hiding them from front-running bots (over 2.1 million users as of 2026)
• MEV Blocker covers over 60% of Ethereum blocks and prevents roughly 80% of sandwich attacks
• Intent-based protocols like CoW Swap use batch auctions where opposing trades match directly, eliminating pool-based slippage on matched portions

Private transaction submission has grown rapidly: over 50% of Ethereum gas now flows through private channels rather than the public mempool.

Why Lightning Payments Have Zero Slippage

Unlike DEX swaps, Lightning Network payments have no slippage by design. A Lightning invoice specifies an exact amount in satoshis. The payment either settles at precisely that amount or fails: there is no partial fill, no price deviation, and no order book to walk through.

This structural difference exists because Lightning is a payment rail, not a price-discovery mechanism. Routing fees are minimal and predetermined rather than variable based on market conditions. Settlement happens in seconds rather than waiting for block confirmation, eliminating the time window where prices could move.

For users who want dollar-denominated payments with instant finality and no slippage risk, Layer 2 solutions like Spark combine Bitcoin's security with fixed-amount settlement.

Mitigation Strategies

For Traders

• Set tight slippage tolerances: use 0.1% to 0.3% for liquid pairs and only widen for illiquid tokens
• Split large orders into smaller trades to reduce per-swap price impact
• Use DEX aggregators (1inch, Jupiter, ParaSwap) that route across multiple pools and sources for best execution
• Trade during high-volume periods when liquidity providers have more capital deployed
• Check pool depth before trading: a $10,000 swap on a $50,000 pool will produce extreme slippage

Protocol-Level Solutions

• Concentrated liquidity (Uniswap V3/V4): LPs focus capital within specific price ranges, providing deeper liquidity at active prices with less total capital. For an in-depth comparison, see the research on Bitcoin DeFi
• Concentrated liquidity market makers improve capital efficiency by orders of magnitude compared to constant product pools
• TWAP (time-weighted average price) execution splits large orders across multiple blocks to average out price impact
• Private transaction submission removes MEV-driven slippage by hiding trade intent from the public mempool

Risks and Considerations

• Slippage is unavoidable on AMMs: it is a mathematical property of bonding curves, not a bug. Even with impermanent loss protections, every nonzero trade on a constant-product pool moves the price
• Transaction reverts waste gas: setting tolerance too tight in volatile markets causes repeated failed transactions, each consuming gas fees with no execution
• Slippage compounds across hops: multi-hop routes (Token A to B to C) accumulate slippage at each step, and the total can significantly exceed expectations
• Low-liquidity tokens can be traps: extreme slippage requirements are sometimes a sign of manipulated pools or tokens designed to extract value from buyers
• Regulatory attention is growing: in July 2025, the European Securities and Markets Authority (ESMA) flagged sandwich attacks as potential market manipulation under MiCA regulation

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.