Slippage tolerance sets how much worse a swap’s execution price may be than its quote before the transaction reverts. For frequent trades on Base, the useful setting is the narrowest one that still clears ordinary price movement and inclusion delay; widening it cannot improve the quoted price. The same trade-off matters when you use BaseSwap, an automated market maker on Base, to swap tokens from your wallet.
What does the tolerance actually limit?
It limits the output shortfall between the quoted swap and execution, not the price impact already shown in the quote. A router encodes a minimum output, often called amountOutMinimum; for an exact-input swap, the transaction reverts if the route returns less.
- Quote versus execution: the quote estimates output from current pool state; tolerance allows that state to move before inclusion.
- Price impact versus slippage: impact comes from your trade moving the pool curve; slippage is the additional movement or adverse execution after the quote.
- Revert versus fill: below the minimum, the swap does not complete, but the failed transaction still consumes network fees.
For example, if a quote is 10,000 units and tolerance is 0.3%, the minimum output is 9,970. A trade that would return 9,969 reverts; one that returns 9,970 or more can execute. These figures are illustrative, and token decimals do not change the percentage calculation.
The tolerance does not cap total loss relative to an external market price. If the pool quote is already poor because the pool is shallow or the swap is large, a tight tolerance can still accept that poor quote. Compare the quoted execution price with a credible reference and inspect price impact separately.
How should you choose a value?
Choose a tolerance from the pair’s volatility, pool depth, trade size and expected delay, then keep the setting low enough to reject a materially worse fill. As a working starting point, 0.1–0.5% can suit deep, liquid pairs in calm conditions; volatile or thinner pairs may need 0.5–1% or more, with a corresponding increase in execution risk.
There is no universally safe percentage. The decisive measure is how far the pool’s executable price can reasonably move during your transaction’s quote-to-inclusion window. Shorter inclusion delay reduces that movement, but a gas tip cannot guarantee priority or prevent a price change before your transaction is processed.
If you are repeatedly widening tolerance to make a route pass, stop and check the quote, pool depth and token behavior. When you use base swap for regular Base trading, treat the displayed quote as the starting point for that check, not as a guarantee of the final fill.
Why can a swap fail even when the market looks unchanged?
A reversion means the on-chain result missed the encoded minimum; it does not necessarily mean the external market moved visibly. Between quote and inclusion, another trade can change reserves, a multi-pool route can move at one intermediate hop, or a stale quote can describe a pool state that no longer exists.
A common mistake is raising tolerance after a failed swap without refreshing the quote. The fix is to refresh first and check whether the route or price impact changed. If the refreshed quote is still attractive but transactions narrowly miss the minimum, a modest increase may be reasonable; if the quote deteriorated, widening tolerance only authorizes a worse fill.
Tokens with transfer taxes, rebasing behavior or unusual transfer hooks can also make router output differ from a simple quote. Whether a route handles those mechanics depends on the token and router implementation; repeated reverts are a reason to verify compatibility rather than keep increasing tolerance.
What does a wider setting cost?
A wider tolerance raises the minimum shortfall you will accept, but it does not charge that percentage as a fee. Pool fees are applied by the pool’s swap logic, while Base transaction costs cover execution and data posting; a reverted attempt can incur those network costs without delivering the tokens.
There is also an execution-quality cost: a permissive minimum leaves more room for adverse movement, including transaction ordering that pushes the pool price against your swap before it executes. The tolerance is not a slippage charge, and a setting of 1% does not mean you will lose 1%; it means the transaction can complete at output up to 1% below the quote, all else equal.
For repeated trading, reduce unnecessary retries by refreshing stale quotes and using a tolerance calibrated to the pair’s ordinary movement. When a trade is large relative to available liquidity, split sizing may reduce curve impact, but extra transactions add network fees and leave more time for prices to move. Compare the aggregate execution result and cost, rather than assuming smaller swaps are automatically cheaper.
What should you check before submitting?
Check the quote age, expected output, price impact, route and minimum received together. Then ask whether the minimum still represents an acceptable trade if price moves against you during inclusion. If not, refresh or reduce size instead of loosening the threshold; that same check keeps a base swap aligned with your intended execution rather than merely making it more likely to pass.