If a volatile token swap fails because the price moved, raise slippage tolerance a little and retry with a fresh quote. Tolerance sets the lowest amount you will accept; it does not guarantee that amount or make a pending transaction faster. Check the quote and expected output first, then choose a limit you can live with.
What does slippage tolerance change?
Slippage tolerance is the maximum price movement you accept between the quote and the swap’s execution. The swap uses it to set a minimum output: if the trade would deliver less, it reverts instead of completing at that worse rate.
For example, if a quote promises 1,000 tokens and you set tolerance to 1%, the minimum is about 990 tokens. At 3%, it falls to about 970. A higher setting makes execution more likely during a sharp move, but lets the trade complete at a less favorable rate.
Two price changes can affect the result. Price impact is the change caused by your own trade using available liquidity; slippage is the extra change while the quote waits to execute. A thin or volatile pair can have both. Raising tolerance accommodates more movement; it does not improve the route or reduce the trade’s price impact.
What should I do when a swap is pending or failed?
A pending swap has not finished on the blockchain, so changing tolerance will not speed it up. Check the wallet’s status and network fee. If the transaction is still pending, wait or use your wallet’s supported speed-up or cancel option; do not submit another swap blindly, since both transactions could execute.
If it fails, read the wallet’s error and check whether the transaction reached the blockchain. A reverted swap may still cost a network fee, even though the tokens were not exchanged. A stale quote, a price move beyond your minimum output, missing token approval, or too little fee to process the transaction can each cause a failure; only the first two point to slippage.
ParaSwap compares routes across liquidity sources, but the chosen route still faces market movement before execution. Understanding how ParaSwap routes token swaps helps explain why a good quote can change while it waits. Check the new quote’s expected output and route before retrying, rather than assuming a higher tolerance will fix every error.
How much tolerance should I set for a volatile pair?
Start with the lowest setting that allows a fresh quote to execute. As a working example, I would try around 0.5–1% for a liquid pair and around 1–3% for a volatile or thinner pair, then adjust only if the error shows the minimum output was missed. These are starting points, not guarantees; the right setting depends on liquidity, trade size, and how quickly the price is moving.
Before retrying, compare the expected output with the amount you would still accept. If a 3% limit means receiving too few tokens, do not raise it just to force the swap through. Reduce the trade size, wait for calmer prices, or choose another route if available. On networks such as Base, also keep enough of the network’s fee token to pay for the transaction.
Choose differently when the pair is extremely thin, the quote shows high price impact, or the token has unusual transfer rules. In those cases, a wider limit can accept a poor execution without solving the underlying issue. Wait, trade less, or skip the swap if the minimum output you can accept is below the fresh quote’s floor.
Top comments (0)