Dodoswap slippage tolerance sets the output boundary for your first swap

Dodoswap slippage can reduce the tokens received between a quote and execution, so check the minimum output before confirming your first swap. Choose a tolerance that keeps that minimum within your acceptable terms. Price impact already affects the quoted exchange, while tolerance allows additional movement during execution. If the minimum falls below the amount you need, revise the unsigned swap or stop. A successful transaction must satisfy its encoded output requirement.

Updated · Thu, Sep 10, 2026

Key takeaway: The minimum received translates your tolerance into a token amount that you can compare with your requirement before signing.

Match the quote to the swap you intend to sign

A usable quote must match the intended network, token contracts, and input amount. Changing any of these means reassessing the output and its minimum.

Confirm the spending prerequisites

The wallet needs the input tokens and enough native currency for network execution. Where the token requires spending approval, the allowance must cover the intended input. An allowance error cannot be solved by accepting a worse exchange rate.

This check passes when the wallet can fund the selected transaction and authorize the required token transfer. If either prerequisite is missing, pause before evaluating a slippage adjustment.

Confirm the output boundary

Read the quoted output and inspect the minimum received associated with the tolerance setting. The quote passes your price check only when its permitted minimum meets your requirement. A pleasing estimated output with an unacceptable minimum leaves room for an exchange you would reject.

Separate price impact from the tolerance setting

Price impact concerns the exchange quoted for your trade size; tolerance concerns how much worse execution may become.

The price effect already inside the quote

A trade consumes available liquidity, so its average exchange rate can worsen as the input amount increases. DODO routing compares liquidity sources, whose available depth differs. A displayed price-impact warning therefore deserves attention before you decide how much further movement to accept.

Lowering tolerance does not remove price impact already reflected in the quote. Even execution exactly at that quote can represent an unfavorable exchange relative to the market price used for comparison.

The movement allowed after quoting

Tolerance gives the transaction room to execute despite a worse outcome than the quote. Other trades or liquidity changes can alter the available output while your transaction waits. Keep the quoted amount, its minimum, and the eventual received amount distinct when assessing that movement.

What does minimum received protect?

Minimum received sets the output floor that a successful swap must meet under the transaction’s checks. For a fixed-input swap, compare that floor with your own required amount in the same output token.

DODO’s routing contract rejects a swap when the checked return amount is below the submitted minimum. Meeting that minimum satisfies the output check; other transaction requirements can still prevent execution. The floor does not reserve liquidity or promise that someone will fill the swap.

View image file

Use the displayed token amount for your decision, especially near a boundary where rounding matters. A tolerance percentage alone does not tell you whether the remaining output is enough for your intended use.

Refresh the quote after setup delays

Time spent arranging an approval or reviewing a wallet prompt can leave the original quote behind market conditions. Obtain a fresh quote before submitting, then reassess its minimum without assuming the earlier amount still applies. A refresh changes the estimate; it does not commit you to accepting it. If the refreshed terms fail your check, keep the swap unsigned.

Choose between Dynamic and Custom tolerance

DODO’s Dynamic setting suggests tolerance using historical transaction data, while Custom lets you choose the setting yourself. Neither selection establishes whether the resulting minimum meets your needs.

Judge the offered setting through the permitted output shortfall. A tighter boundary leaves less room for adverse movement and can cause more failures when prices change. A wider boundary permits worse execution. Increasing it makes sense only if those newly permitted terms are acceptable, rather than merely because an earlier attempt failed.

The gap also matters when transaction ordering exposes a swap to a sandwich attack. An attacker can trade around a pending swap to worsen its execution within the accepted boundary. A tight tolerance restricts that room without establishing complete protection against such attacks.

What can cause a swap to fail besides slippage?

A failed swap can reflect missing approval, insufficient funds, an expired deadline, or a contract condition unrelated to tolerance. Read the available error before changing the permitted output.

An insufficient-return error points to the output boundary. Refreshing the quote can show whether the trade still meets your requirement. If it does not, retaining that boundary prevents an unwanted exchange; repeated failure is not evidence that the boundary should move.

A deadline failure has a different cause. DODO’s routing contract checks transaction expiry separately from minimum output. Increasing tolerance does not extend an already submitted deadline.

Pool checks can also stop execution independently. DODO V3 includes checks on pool operation and market-maker heartbeat, alongside its output requirement. A failed simulation therefore needs attention to the reported condition, rather than an automatic tolerance increase.

Compare a smaller amount with a different route

A smaller input can reduce price impact when trade size is large relative to available liquidity. Compare output per input token, because reducing the input naturally reduces the total output as well.

DODO routing can use intermediate tokens and split trades across pools. Different paths expose the trade to different liquidity depths and execution costs. Restricting routing to direct pools removes intermediary paths, which can also remove an available exchange. Compare the resulting quote and minimum without assuming fewer steps always produce better terms.

If the available minimum remains unacceptable, waiting leaves the swap uncommitted. Where a suitable limit order is available, its specified price offers a different execution condition, with the possibility that the order remains unfilled.

Compare the received amount with the submitted floor

After execution, assess slippage against the saved quote and the minimum encoded in the transaction you submitted. A newly refreshed quote describes different market conditions and cannot measure that transaction’s original price movement.

For a fixed input and comparable token amounts, the output shortfall percentage equals the quoted amount minus the received amount, divided by the quoted amount, multiplied by 100. Keep network costs separate from this token-output calculation. A negative result means the received amount exceeded that quote.

Order history can identify the completed swap, but the relevant comparison is its actual output against its saved threshold. An unexplained mismatch needs reconciliation before another attempt. Repeating a successful swap creates another exchange; it does not correct the first one’s execution price.