Why slippage exists on-chain
When you swap on a decentralized exchange, you trade against a liquidity pool or an aggregator route through several pools. Pool prices follow a formula (constant-product AMMs are the classic example). Every trade nudges the ratio of tokens in the pool — so the effective price for the next unit is slightly different from the last.
Between the moment you fetch a quote and the moment your transaction lands in a block, other traders can move the same pool. Validators order transactions by fee and timing. That gap — quote time vs execution time — is what users usually mean by slippage in crypto swaps.
Your wallet or aggregator converts that uncertainty into a slippage tolerance: “I will accept any execution price up to X% worse than the quote.” If the on-chain outcome would exceed X%, the swap reverts and you pay gas without receiving tokens.
Slippage vs price impact
These terms overlap in casual chat but measure different things:
- Price impact is how much your trade size alone moves the pool price at execution time, assuming nothing else changes. Large trades into thin pools show high impact even in a quiet market.
- Slippage (tolerance setting) is the maximum adverse move you allow between quote and execution — including other people’s trades and volatility during the block.
A small trade in a deep pool might show low price impact yet still need non-zero slippage tolerance during volatile news, because the quote can age out before confirmation. Conversely, high price impact means you are hurting your own price even if the market stands still — splitting the order or picking another route may help more than raising slippage.
Cranking tolerance does not create liquidity. It only increases the worst price you might accept — including sandwich-style losses on public mempools. Fix impact by trading smaller size or waiting for deeper liquidity.
Minimum received and your tolerance
Good swap UIs show two numbers: expected receive and minimum received. The minimum is typically:
minimum ≈ quoted receive × (1 − slippage tolerance)
On EVM routes through LI.FI, the quote payload includes fields like expected output and toAmountMin — the floor the route guarantees if the transaction succeeds. Jupiter quotes for Solana follow the same idea in their swap response before you build the transaction.
If minimum received is uncomfortably far below spot price, the problem is usually impact, fees, or a multi-hop route — not a bug in the wallet. GaurdWallet surfaces live quotes from proxied APIs; it does not fabricate rates.
Offline minimum calculator
Type the quoted receive amount from Exchange (not the pay amount) and your slippage percent to see the arithmetic floor. Confirm the real minimum on screen before signing.
Presets: 0.5%, 1%, and 3%
GaurdWallet Exchange offers quick slippage presets plus custom values. Practical starting points:
| Preset | When it fits | Trade-off |
|---|---|---|
| 0.5% | Deep pairs (ETH/USDC on major L2s), calm markets | More revert risk if mempool is busy |
| 1% | Default-style balance for many everyday swaps | Moderate protection vs fill rate |
| 3% | Volatile altcoins, thin pools, fast-moving news | Wider worst-case fill; review minimum received carefully |
Bridges that include swap legs inherit the same tolerance concept on the swap portions. Longer bridge durations mean quotes expire — refresh rather than raising slippage without understanding impact.
When swaps fail
Common revert reasons:
- Slippage exceeded. Market moved past your tolerance before execution.
- Insufficient allowance or balance. Approval not confirmed, or amount plus gas exceeds holdings.
- Expired quote. Aggregator routes time out; GaurdWallet should prompt a refresh — never sign stale numbers.
- Token fee-on-transfer quirks. Some tokens tax transfers; routers may revert if not supported.
Failed transactions still consume gas on EVM chains. That is normal — slippage protects you from a bad fill, not from network fees.
Slippage in GaurdWallet Exchange
On Exchange, pick Swap (EVM or Solana), enter amount, set slippage, wait for the proxied quote, and read minimum received before confirm. EVM swaps may require an exact-amount ERC-20 approval first — see ERC-20 token approvals.
Solana swaps via Jupiter add priority-fee choices at the protocol level; slippage still bounds output. Solana is same-chain only in v0.2.1 — no Solana↔EVM bridge in Exchange.
For a full walkthrough of approvals, bridge status cards, and unsupported networks, read how to swap and bridge in GaurdWallet or browse the swap & bridge hub.
FAQ
Is slippage a fee? No. Fees go to validators and liquidity providers. Slippage is price movement (or allowed price movement).
Should bridges use higher slippage? Only if the route includes swap legs that need it. Bridging stablecoins across major EVMs may still need patience for quote refresh, not necessarily 5% tolerance.
Does GaurdWallet front-run me? Non-custodial signing means you broadcast through public infrastructure like any wallet. Use reasonable slippage and avoid suspicious tokens.
MEV, sandwiches, and realistic expectations
On public EVM mempools, searchers sometimes reorder trades around large swaps — a “sandwich” pattern. Tighter slippage limits how much you can be extracted, but cannot eliminate mempool competition. Private routing or L2 sequencers change the picture; treat slippage as one layer of defense, not a guarantee of perfect mid price.
On Solana, Jupiter routes land in a different fee market; priority fees influence ordering. Read both slippage bounds and fee settings when trades fail during NFT mints or memecoin spikes.
When learning, compare your executed output to the quote shown seconds earlier — small drift is normal; large drift means you should revisit impact, tolerance, or route choice before sizing up.
How to pick a tolerance in practice
Start with the lowest preset that still confirms during a test trade on the pair you care about. If your transaction reverts twice with 0.5%, try 1% on the third attempt while watching minimum received — not blindly jumping to double-digit tolerance.
For stablecoin-to-stablecoin swaps on deep pools, tight slippage is reasonable because price impact should be tiny. For launch-day tokens, even 3% may be tight; consider whether you should trade at all when impact warnings flash.
Bridge quotes that embed swap legs inherit tolerance on those legs. A bridge showing multi-minute duration gives more time for market drift; refresh the quote if you stepped away before signing.
GaurdWallet shows live numbers from proxied aggregators — compare expected and minimum on every confirm. If you need a deeper split between impact and tolerance metrics, watch for the dedicated swap & bridge hub article on price impact vs slippage (planned in this cluster).
Slippage on bridge routes that include swaps
When LI.FI composes a bridge plus DEX legs, each swap leg respects your tolerance independently in the encoded transaction. A stablecoin bridge might show tight minimum received while an embedded altcoin swap leg dominates risk. Expand the route preview when Exchange offers it.
Longer executionDuration estimates mean more time for prices to drift between quote and final destination credit. Refresh before signing if you paused mid-flow — the same discipline described in guides about why swap quotes expire.
Test with small notional when learning a new corridor. A revert on a $5 trade teaches the same lesson as a revert on a $500 trade, minus the emotional tax.