Set slippage tolerance to the largest drop in output you would accept between the quote and execution; for a liquid token pair, start low and check the minimum you will receive. The right setting depends on price movement and liquidity while your transaction waits. Raising it can help a swap execute, but permits a worse price.
What does slippage tolerance actually limit?
Slippage tolerance sets a boundary for execution; it does not improve the quoted price. For an exact-input swap, the app usually calculates a minimum output from the quoted amount and your tolerance. If execution would deliver less, the transaction should fail instead of completing below that floor.
Say a quote estimates 2,000 USDC and your tolerance is 0.5%. The minimum is 1,990 USDC: 2,000 × (1 − 0.005). A quote of 2,000 USDC already reflects the route’s estimated price impact; the tolerance allows for further movement before execution. Check the app’s displayed minimum received because fees or route details may affect its calculation.
How should you choose a setting?
For a liquid pair, I would start around 0.1–0.5% as an example range, then judge the quote and minimum amount rather than automatically accepting a higher default. A volatile or thinly traded token can move further while the transaction waits, but a wider setting also allows you to receive less. There is no percentage that makes every trade safe.
Compare the estimated output and minimum received with the amount you are willing to accept. In a ParaSwap token swap, that check matters even when the aggregator finds a competitive route: the route’s estimate can change before it executes, and the minimum is the actual floor you are accepting. If the floor is too low, refresh the quote or reduce the trade size instead of raising tolerance by habit.
Price impact and slippage are different. Price impact comes from the trade’s size relative to available liquidity and is already reflected in the quote; slippage tolerance covers additional price movement before execution. A large price impact is a reason to reconsider the route or amount, not to increase tolerance until the trade goes through.
What should you check before confirming?
Review the output token, estimated amount, minimum received, network, and any separate network fee. A swap that fails can still consume network fees because the transaction used computation before reverting. If the quote changes while you are reviewing it, refresh it and inspect the new minimum rather than relying on the earlier figure.
What if the swap keeps failing?
A failure often means the price moved beyond your limit before execution, or the quote became stale. Refresh the quote and try a smaller trade, which may face less price impact. Only raise tolerance if you have checked the new minimum and are willing to receive that amount; a higher setting can let execution proceed at a worse price.
Does a higher tolerance make a swap faster?
No. It changes the price boundary for execution, not how quickly the transaction is processed. Network congestion, transaction fees, and the chain’s block timing affect confirmation. Increasing tolerance may reduce failures during volatile movement, but it cannot guarantee a quick confirmation or a particular final price.
Top comments (0)