Slippage is the difference between the price a swap is quoted at and the price it actually executes at. It happens because an automated market maker prices from the token balances sitting in its pool, and those balances can change between the moment you are quoted and the moment your transaction is included in a block — other trades land first and move the pool. Slippage is distinct from price impact, which is the price movement your own order size causes against the pool's depth, and from fees, which are known before you trade. The slippage-tolerance setting is a guardrail rather than a prediction: it instructs the swap contract to revert if you would receive less than a stated minimum received. No wallet can abolish slippage, but in WATS the swap is signed inside a fully non-custodial wallet — you hold the keys, and WATS never holds one — with the quote, the tolerance and the minimum received shown before the signature.
The price you saw vs the price you got
Every swapper meets it eventually: the quote said one rate, the confirmation shows another. That gap is slippage — the difference between the price you were quoted and the price your trade actually executes at. It is not a scam and usually not a bug; it is a structural property of how on-chain markets work. But left unmanaged, it quietly taxes every trade you make — and in the worst cases it is the opening an attacker walks through.
Where slippage comes from
Most on-chain swaps run against automated market makers — liquidity pools whose price is a function of their token balances. Two consequences follow. First, your own trade moves the price: buying from a pool makes the asset scarcer in it, so the marginal price rises as your order fills — the bigger your trade relative to the pool, the worse your average rate. Second, other people trade too: between the moment you were quoted and the moment your transaction lands in a block, other swaps may have shifted the pool. Quote-time price and execution-time price are simply measured at two different moments on a moving market, and the wait between them is not instant — on EVM chains your transaction sits in a public mempool until a block builder includes it, and on chains that stream transactions straight to the next block producer it still waits, just less visibly.
Slippage tolerance: what the setting actually does
The slippage setting in a swap interface is a guardrail, not a prediction. Setting 0.5% tells the contract: execute only if I receive at least 99.5% of the quoted output — otherwise revert. That reverting is a feature. A failed swap costs you a network fee but keeps your tokens; a swap that fills 12% below quote costs you real money with no receipt. The number to actually read before signing is minimum received — the worst case you are agreeing to, stated in tokens rather than percentages. Most routers pair it with a deadline: a timestamp after which the swap can no longer execute, so a transaction stuck for an hour cannot suddenly fill against a market that has moved on without you.
Slippage vs price impact vs fees
Three different things reduce what you receive, and interfaces often blur them into a single number. Fees — the pool's cut and the network fee — are known upfront. Price impact is the price movement your own trade size causes against the pool's depth; it exists even on a perfectly calm market with nobody else trading. Slippage is the movement between quote and execution caused by everyone else. Fees you accept, price impact you reduce by trading smaller or routing through deeper pools, slippage you cap with tolerance. Diagnosing which one hurt you tells you which lever to pull: raising tolerance does nothing about price impact, and splitting the trade does nothing about a fast-moving market.
When slippage turns dangerous
Two situations deserve respect. Thin liquidity — small pools, new tokens, exotic pairs — where even modest trades cause double-digit price impact, and where a generous tolerance quietly authorizes a terrible fill. And hostile flow: on chains with a public mempool, pending transactions are visible to anyone before they confirm, so a high slippage tolerance is an invitation for sandwich bots to buy ahead of you, let your order push the price, then sell back into it — consuming almost exactly the margin you allowed. The rule of thumb: your tolerance is not a convenience setting; it is the size of the loss you are pre-approving.
Practical settings that work
For deep, stable pairs, keep tolerance tight — a fraction of a percent — and let the occasional revert protect you. For volatile or thin tokens, raise it deliberately and in small steps, knowing what you are granting. Split unusually large trades so each piece causes less impact, and prefer routes through deeper liquidity even when the headline quote looks slightly worse. And make reading minimum received a reflex before every signature — it is the single most informative number on the screen. The broader mechanics of in-wallet swapping are covered in how to swap tokens cross-chain safely, and the multi-chain version in swapping and bridging across chains.
How WATS fits in
Slippage is a property of the market, so no wallet can abolish it; what a wallet decides is whether the guardrail sits in front of you before you sign. WATS keeps swaps inside a fully non-custodial wallet — you hold the keys, and WATS never holds one — with the quote, the slippage tolerance and the minimum received shown before the signature, across Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Solana and TON. It also removes the failure mode that pushes people into careless retries: every action — transfers, swaps, staking — is charged in one token, ATS, instead of each chain's native gas token, via an ERC-4337 paymaster on EVM and an equivalent fee-payer on Solana and TON, so a swap never stalls because you are short of gas on the network you happen to be trading on. That is not a discount: the ATS fee tracks the live network cost, and it changes which token pays rather than what the transaction costs. ATS is a LayerZero OFT, so it is one balance across all three ecosystems, and collected ATS is burned from a 100M supply toward a 30M floor — WATS is the first and only wallet to combine ERC-4337 and OFT single-token fees with that burn, described on the ATS fee page. If you want the discipline in this post to be the default rather than something you have to remember — tolerance set deliberately, minimum received read before every signature, no scramble for a gas token mid-trade — running the swap in WATS is the concrete way to get it.
Frequently asked questions
What is a good slippage setting?
For deep, liquid pairs, a tight tolerance of a fraction of a percent is usually right — occasional reverts are the protection working. For volatile or thinly traded tokens you may need more, but raise it deliberately: your tolerance is the worst-case loss you are pre-approving, and a high setting also widens the margin sandwich bots can extract. Always check the minimum-received figure before signing, because that is the worst case stated in tokens rather than percentages.
Is slippage a fee?
No. Fees — the pool's cut and the network fee — are known before you trade. Slippage is price movement between your quote and your execution, caused by other trades landing first; price impact is the movement your own trade size causes against the pool's depth. They reduce your output through different mechanisms, and each has a different remedy: accept fees, reduce impact by trading smaller or in deeper pools, and cap slippage with your tolerance.
Why did my swap fail with a slippage error?
Because by execution time the pool could no longer deliver at least your minimum received, so the contract reverted rather than fill you at a worse rate — the guardrail doing its job. It usually means the market moved quickly or the pool is thin. You can retry, slightly raise tolerance in small steps, or split the trade; treat repeated failures on a thin token as a warning about its liquidity rather than an obstacle to force through.
Does the wallet I use change how much slippage I pay?
No wallet can remove slippage — it comes from the pool, not the app — but WATS puts the controls in front of the signature: the quote, the slippage tolerance and the minimum received are shown before you sign, and the wallet is fully non-custodial, so you hold the keys and WATS never holds one. WATS also charges network fees in a single token, ATS, via an ERC-4337 paymaster on EVM and an equivalent fee-payer on Solana and TON, so a swap on Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, Solana or TON does not stall because you are short of that chain's native gas token. That matters in practice, because a scramble for gas mid-trade is exactly when people raise their tolerance carelessly.