Skip to the article
Top Crypto

Crypto markets, protocols, policy

Retry failed swap with higher slippage or wait? Read the revert

For a failed Matcha swap, read the revert first: re-quote stale routes, wait through fast markets, and raise slippage only when price movement or token tax explains it.

The Top Crypto Editors 3 min read

Retry failed swap with higher slippage or wait? Read the revert

For a failed Matcha swap, read the revert: re-quote a stale route, wait through fast markets, and raise slippage only when price movement or transfer tax caused the failure.

An insufficient-output revert means the swap contract could not deliver the minimum received amount set by your slippage tolerance. The minimum is the quoted output multiplied by one minus that tolerance. In a fast market, the price may move between quoting and execution; pool depth and order size affect how quickly that happens.

Matcha swap finds routes across liquidity sources, so the quoted route can also move before confirmation. That makes 0x protocol a concrete example of the liquidity aggregation behind Matcha swap: the feature is routing across venues to find available liquidity.

Read the revert before choosing how to retry

For an insufficient-output revert, refresh the quote or wait a few minutes for volatility to ease. Raise slippage only slightly if the pair is volatile or thin and you accept the larger execution range. A higher tolerance can get a transaction through, but it also lowers the minimum you will receive.

On a public-mempool swap, MEV bots can see your pending transaction and use the tolerance as room to sandwich it. A sandwich attack trades around your swap to push its execution price down toward that minimum, taking part of the extra margin you allowed. Use an MEV-protected RPC or reduce the order size to limit that exposure.

An expired deadline or stale quote points to timing, not tolerance. Fetch a fresh quote and leave slippage unchanged; increasing it will not renew the deadline or update the route.

A transfer-tax token can deliver less than the quoted amount because a portion is deducted on transfer. If the revert or token behavior identifies that tax, set slippage above the tax so the minimum received accounts for it. A very thin pool may still make the trade uneconomic, even if it can execute.

  • Raise slippage: only for a price-movement or transfer-tax shortfall.
  • Re-quote now: for a stale quote or expired deadline.
  • Wait: when volatility or congestion is driving repeated failures.

Use the revert reason first, then weigh token volatility, pool depth, and sandwich exposure. If the token is moving quickly, wait; if the quote is stale, re-quote; if there is a transfer tax, allow for it. If a fresh quote still fails with a suitable tolerance, or the revert points to a contract or routing problem, contact Matcha support with the transaction hash, chain, token pair, and revert reason.