Set Swap Slippage for Repeat Trades by Starting With the Quote

For fast, repeat swaps, set slippage just wide enough to cover likely price movement before execution, then check the output again before each trade. A swap interface estimates how many output tokens a route should return; the transaction sets a minimum amount you will accept. If the route returns less, the swap reverts. If it returns at least that minimum, it can execute.

What does a slippage setting control?

Slippage tolerance sets how far the output may fall below the interface’s estimate before the transaction fails. For example, a setting of 1% on a quote for 100 output tokens would generally set a minimum near 99, subject to the protocol’s calculation and fees. The contract checks that minimum against the amount available when the swap executes.

The estimate can change while a transaction waits to be included in a block. Other swaps may change the pool’s token balance and price first. A larger trade can also move the pool price as it uses available liquidity; that effect is called price impact and is reflected in the quote. Slippage tolerance is the extra movement you agree to accept after that estimate.

For the wider distinction between swapping, adding liquidity and staking, the biswap explainer gives the fuller account. Here, the practical point is that each new swap starts from a fresh quote, even if the token pair and trade size stay the same.

How should you choose a setting for repeat swaps?

Choose the narrowest tolerance that lets the trade clear under the conditions you expect. There is no universal percentage: the useful setting depends on the pair’s liquidity, trade size, price movement and any token transfer fees. A deep pool and a small trade may need less room than a thin pool or a large order.

Use each quote as the starting point. Check the quoted output, the route, the displayed price impact and the minimum output. If a trade reverts, refresh the quote and inspect what changed before widening the tolerance. A tighter setting can fail more often when the price moves quickly, and a failed on-chain transaction may still consume network fees. A wider setting lowers the chance of a revert but lets the transaction execute at a worse output than the quote.

For a sequence of trades, repeat the check each time:

• Refresh the quote and confirm the token pair and route.
• Compare the quoted output and price impact with the previous trade.
• Set the minimum output from the current quote and your chosen tolerance.
• After execution, compare the actual output with the quote before placing the next swap.

This is like checking a new fare before each leg of a journey: the last price is useful context, but it does not guarantee the next one. Reusing the same percentage can be convenient, but it should not replace checking the quote and minimum output.

When should you change the tolerance?

Change it when the evidence points to a mismatch between the setting and the trade, not just because one swap failed. If the quote has moved or the trade is large relative to the pool, reduce the order size or wait for conditions to settle before granting a wider range. Splitting a large order can reduce its price impact, though multiple transactions add fees and each leg gets a new quote.

If repeated trades fail at a narrow setting, first check whether the token charges a transfer fee or has trading restrictions. Such rules can reduce the received amount or prevent the swap; a wider tolerance is not a reliable fix. Only allow for a known fee if you understand how the token applies it and the interface’s quote accounts for it.

For most repeat trading, the better habit is to keep the tolerance conservative, refresh the quote before every swap, and respond to failures by checking the route, liquidity and token rules. Raise the limit only when you can explain what extra movement it covers. That keeps the minimum output meaningful while still giving a fast-moving trade room to execute.