Why Tiny Swaps Fail Minimum Output Checks

A tiny swap fails a minimum-output check when the trade delivers fewer tokens than its transaction allows. The app estimates the output, applies a slippage limit, then sends that minimum to a router contract. The router follows the token route through one or more liquidity pools. If the final amount falls below the minimum, the transaction reverts.

In Uniswap v2’s router guide, the minimum is called “amountOutMin”: the least output accepted for an exact-input trade. The same idea helps explain why a small order can fail. The check compares two token amounts; it does not know whether a trade feels small in dollar terms. For the broader questions to ask before a trade on Avalanche, see questions to ask before a Blackhole swap. In practice, the failure message alone may not identify whether the floor, quote or route caused the mismatch.

How does a minimum-output check work?

The app starts with the input amount and estimates how much the route can return. A route may use one pool or pass through an intermediate token. The app then lowers its estimate by the chosen slippage tolerance and encodes the result as the minimum output. The router executes the swap and checks the final amount against that floor.

Think of the minimum as a limit on a parcel’s delivery: the sender accepts the trade only if at least the stated quantity arrives. A looser slippage setting lowers that floor, making execution more likely but allowing a worse exchange rate. A tighter setting raises it, offering more protection against price movement while making a revert more likely.

Why can a small trade fall below the minimum?

A small input usually produces a small output, so the relevant amounts can approach the smallest unit the output token supports. Tokens store balances as integers in base units. If a calculation rounds down, the app’s displayed estimate may look like zero, or the contract’s output may be lower than a minimum rounded or configured differently.

Pool fees also reduce the output, and a trade moves the pool price as it uses liquidity. Those effects apply to large trades too, but on a tiny trade the output can be close enough to a rounding boundary that a difference of a few base units matters. A fixed minimum trade size set by an app or route can have a similar effect. That is separate from the router’s slippage check, even if the app presents both as a swap failure.

What should you check when a tiny swap reverts?

Check the quoted output, the minimum received, and the transaction’s failure reason before changing settings. Those values help separate a strict floor from a stale quote or a route that cannot execute. Then check whether the output is being rounded for display or whether the app imposes its own minimum size.

• Compare the quoted output with the minimum received. If they are nearly equal, even a small price move may cause a revert.
• Refresh the quote. Pool prices and available liquidity can change between the estimate and execution.
• Check the token’s displayed precision. A rounded display of zero does not always mean the raw output is zero.
• Check the wallet’s input balance, token approval and native-token balance for network fees. These can block a transaction for reasons separate from minimum output.

Should you lower the slippage setting?

Lowering the minimum can help when the quote is sound and ordinary price movement is pushing execution below the floor. It also accepts a worse rate, so it is not a general fix for a tiny swap. If the calculated output rounds to zero or the app has a fixed size limit, changing slippage may not help.

For most readers, the better first move is to refresh the quote and inspect the minimum received. If the trade remains too close to the token’s smallest units, increasing the input may give the route room to clear its rounding and fee costs. If the quote has moved sharply, wait and check again. The minimum-output check is doing its job when it rejects a trade that no longer meets the rate you accepted.