Academy glossaryDecision concept

Slippage

Slippage is not only volatility. It can come from low liquidity, route depth, market movement, or the size of your own order relative to available liquidity.

This term should change

If liquidity is thin or size is large, assume you need more caution before you need more tolerance.

Routes that only clear when you keep increasing slippage tolerance.

volatile route during quote refresh

How to use this lesson

Use the lesson summary first, then move straight into the decision split that changes the real tradeoff.

Treat every example below as product context for the same judgment, not as separate glossary trivia.

Keep the later applied and rule sections as support layers, not the main event.

Lesson summary

What slippage should change in your behavior

Slippage is not a random annoyance setting. It is the damage limit you are willing to accept before the trade stops being acceptable.

It is a damage boundary

Slippage tolerance tells the route how much execution drift you still accept before the trade should fail.

High slippage is not a fix

If you only get execution by stretching tolerance, the route quality or trade size is usually the real problem.

Size often matters more

Reducing size is often cleaner than forcing the same weak route through wider tolerance.

Decision point

Low vs high slippage in plain English

Users usually do not need a perfect number. They need to understand what kind of failure each direction is buying.

Lower slippage

Better when you want stronger price protection and you are willing to let the route fail if conditions move.

Protects min received more aggressively.

Can fail more often in volatile or thin conditions.

Cleaner when execution quality matters more than immediate completion.

Higher slippage

Defensible only when you know why the route needs extra room and still accept the worse possible fill.

Increases the chance the transaction goes through.

Also increases how much execution drift you may end up accepting.

Needs stronger justification when liquidity is thin or the route is unstable.

See it in product

These are the three fastest anchors for live use: where the term first appears, what to treat as the warning sign, and which rule should change your next move.

Spot first

volatile route during quote refresh

Watch for

Routes that only clear when you keep increasing slippage tolerance.

Rule

If liquidity is thin or size is large, assume you need more caution before you need more tolerance.

Core lesson

Use the term in context

Work through the main concept first, then move into applied judgment and next actions.

What slippage actually changes

Slippage tolerance is not a setting for getting a better price. It is a setting for how much price movement you are willing to tolerate before the trade should fail.

Too low and the transaction may fail even if the route is fine.

Too high and the trade may execute under much worse conditions than you expected.

Fast-moving markets and shallow liquidity make slippage matter more.

Cross-chain routes stack timing risk on top of the usual slippage problem.

Set slippage as a risk boundary, not as a magic knob for convenience.

Real cases

What actually happened

These are public cases and repeated real-world patterns turned into teachable stories. Use them to see how small shortcuts become expensive outcomes in real product flows.

Public source-backed

Read the story first, then notice the exact decision that made the damage possible.

Case study

Stablecoin swap, mempool exposure, six-figure damage

Loss: $215K+

Situation

In a widely reported March 2025 sandwich-attack case, a trader tried to swap about $220,764 of USDC for USDT on Uniswap v3. On the surface it looked like the safest kind of trade: stablecoin into stablecoin.

Why this case matters

One real-world failure usually teaches faster than ten abstract warnings.

What they assumed

The trade looked too boring to be dangerous, so execution mechanics like MEV exposure and slippage felt less important than they really were.

Red flag you would have seen in the UI

A large size, a public route, and a swap that still depended on execution timing rather than a guaranteed fixed outcome. In product terms, this is the moment to look harder at route quality and min received instead of relaxing because both tokens look stable.

You would have seen this on

These are the exact product moments where this kind of mistake usually first looks harmless.

QuoteProvidersRouteSlippage

What went wrong

The transaction was visible in the public mempool before execution.

MEV bots were able to sandwich the trade and distort the pool around it.

The trader reportedly received only about $5,271 in USDT instead of anything close to the expected amount.

What looked like a routine stablecoin conversion became a loss of more than $215,000 within seconds.

Core lesson

Stable assets do not make execution mechanically safe. Slippage discipline, route quality, and MEV exposure still matter when the trade looks boring.

What they should have done instead

Treat even stablecoin routes as real execution events. Check route quality, keep slippage disciplined, and avoid assuming 'boring asset pair' means 'safe execution.'

Source

Publicly reported MEV sandwich case, March 2025

Core points

Carry this into live execution

It decides whether a quote still remains acceptable once the market or route shifts before execution.

It shapes the minimum amount you are willing to accept before the trade should revert.

It becomes more sensitive as order size grows relative to available liquidity.

It is one of the main reasons a route that looks best can still produce a disappointing outcome.

Use after the lesson

Before you sign or confirm

This section should help in the moment of risk. Keep one question in mind: what should I check right now before giving authority or sending the route forward?

Check now

Do not think in abstract principles here. Think in checks you can do on this screen before moving forward.

Do now

Treat slippage tolerance like a line of defense.

Reduce size before you blindly widen tolerance.

Recheck min received whenever the quote refreshes in a fast market.

Do not continue if

Do not use high slippage as a shortcut around bad route quality.

Do not ignore price impact while adjusting slippage.

Do not assume a trade should go through just because the UI allows it.

Red flag if this feels routine

If this step feels like harmless friction, that is already the red flag.

Routes that only clear when you keep increasing slippage tolerance.

Thin liquidity where small market moves can suddenly change min received.

Cross-chain routes where delay makes normal slippage assumptions less reliable.

Before first serious use

If these checks are not clear yet, you are not in a good position to rely on speed or instinct.

Before raising slippage

Check whether the route or token liquidity is the real issue.

See if a smaller size solves the problem more cleanly.

Re-read min received after the latest quote update.

Decide whether waiting is better than forcing execution.

Use after the lesson

Decision flow

Do not use this like a reading section. Use it as the order of operations when the screen is asking for authority or final confirmation.

How to think through it

Step 1

Start with the route, not the setting

If slippage already feels high, first ask whether the route is thin, volatile, or too large for the available liquidity. Do not start by forcing the setting upward.

Step 2

Check min received

Min received is where the trade stops being acceptable. If that number already feels bad, the trade is weak before you touch the slippage control.

Step 3

Adjust size before tolerance

Smaller size often fixes the real problem more cleanly than a wider tolerance. This is especially true when price impact is doing part of the damage.

Step 4

Only widen when you understand the reason

If you widen slippage, do it because you understand the market condition and still accept the downside, not because the button keeps failing.

Signals to notice

Quote keeps refreshing lower in a fast market

That usually means the trade is unstable right now, and forcing it through can turn a decent idea into a bad fill.

A small size increase sharply worsens the route

That is a sign the liquidity is more fragile than it first looked.

You only get execution by raising slippage a lot

That often means the route quality is weak or the trade size is wrong for the market.

Rules

Decision rules

If liquidity is thin or size is large, assume you need more caution before you need more tolerance.

If a route is cross-chain, remember that timing risk stacks on top of normal slippage risk.

If raising slippage is the only way a trade works, ask whether the trade should be smaller or delayed instead.

Use min received as the real guardrail when deciding whether the trade still makes sense.

Avoidable errors

Common mistakes

Treating slippage as a harmless setting that only affects transaction success.

Raising slippage aggressively without checking route depth or token liquidity.

Ignoring the difference between volatility-driven movement and self-inflicted price impact.

Assuming the best quote remains the best quote after conditions move.

Practice

Short scenarios

Use quick situations like these to test whether the concept would hold up in a real product flow.

Large order into thin liquidity

A route shows a decent headline output, but the pool is shallow and your trade size is large relative to visible liquidity.

Do not solve this by blindly raising slippage. First reduce size, inspect price impact, and decide whether the route is still acceptable after fee drag and min received.

Fast market, quote looks stale

The quote was fine a few seconds ago, but the market is moving and route refreshes keep changing the output.

Treat slippage as a limit on damage, not a way to force execution. If the route keeps moving, waiting or reducing size can be better than widening tolerance.

Continue learning