Minimum output protection sets the price a swap will refuse

Minimum output protection sets the least amount of a token a swap will accept, and the transaction fails if the market can no longer deliver it. That floor turns a quoted price into an execution condition: a trade either meets the user’s limit or does not happen. Without it, a swap may complete for fewer tokens than expected after the pool changes. The protection is useful, but it cannot guarantee the quote, prevent every loss, or make a thin market liquid.

What does minimum output mean in a crypto swap?

Minimum output, often shown as “minimum received,” is a threshold written into the transaction. A swap interface estimates how many tokens the trade should return, then subtracts a permitted amount of slippage to set that threshold. If the route can deliver at least that many tokens when the transaction executes, it proceeds. If not, it reverts.

For example, a quote might estimate 100 units of the token being bought, with a minimum output of 98. The trade can settle anywhere from 98 upward; the quoted 100 is not a promise. If the route can return only 97, the transaction should fail rather than silently accept the worse result. The threshold is denominated in the output token, so it is more direct than setting a maximum price in the input token.

The estimate and the threshold do different jobs. The estimate describes the route’s expected result at the time of quoting. Minimum output limits how much that result can deteriorate before execution. It does not ensure that the estimate was fair to begin with, nor does it cap network fees or protect a trader from a token whose value changes sharply after receipt.

Why can the amount received change after a quote?

A quote can change because the transaction executes against market conditions that differ from those used to calculate it. In an automated market maker, a trade changes the ratio of assets in a pool; larger trades relative to the pool’s liquidity generally move the price more. Other trades may also land first and change the available reserves. Network delay, congestion, and route changes can widen the gap between quote and execution.

Price impact is the effect of the trade itself on the pool price. Slippage is the difference between the expected and executed result, which can reflect price impact as well as intervening market movement. They are related but not interchangeable. A large trade in a shallow pool can have high price impact even if no other trader acts. A small trade can still suffer slippage if the market moves before it is included.

For trades routed through several pools, the final output depends on each leg. A router may find a better route than a single pool, but its estimate can still become stale. Cross-chain swaps add another distinction: some flows perform a source-chain swap and then a separate destination-chain action, with different execution points and failure rules. For a fuller account of how a Super Bridge wallet transfer and its swap steps work, see the dedicated guide; here, the key point is that a single minimum-output setting may not describe every stage of a cross-chain flow.

How should you choose a minimum output setting?

Choose a threshold that reflects the amount of execution variance you are willing to accept, while checking that the underlying quote and route make sense. A tighter threshold rejects more trades when conditions move, while a looser one allows more variation in the amount received. Neither setting improves the market price; it only changes the point at which the transaction stops being acceptable.

• Check the quoted output and the minimum received before approving the swap.
• Compare the route and price impact, especially for a large trade or a thinly traded token.
• Use a tighter tolerance when the quoted amount matters more than completing quickly.
• If a transaction repeatedly fails, review the market and route before widening the tolerance.

Interfaces differ in how they expose this choice. Some set a default tolerance and let users change it; others show a minimum received figure without making the underlying percentage prominent. Read the output amount itself rather than assuming a familiar default is appropriate. A very tight setting can cause repeated reverts in a volatile or congested market. Repeated retries can cost network fees even though the swap does not complete.

What does minimum output protect against, and what should you watch?

Minimum output protects against a swap settling below its chosen floor, including some forms of adverse price movement while a transaction waits. It does not stop a transaction from being targeted or guarantee that every included trade is optimal. A broad tolerance may leave room for an unfavorable execution; a narrow one may make the transaction fail instead. The trade-off is between accepting a wider range of outcomes and accepting the possibility of no swap.

Before signing, verify the token being received, the route, the quoted output, and the minimum. If the displayed figures are far apart, understand why before proceeding. For a cross-chain flow, check whether the quoted minimum applies to the source swap, the destination amount, or both; interfaces may present these stages differently. A wallet approval to spend a token is also separate from the swap itself, so check the requested token and allowance.

After submitting, the useful signals are whether the transaction confirms or reverts, the actual amount received, and any change in the route or quoted minimum before execution. If a trade fails, reassess liquidity and price movement rather than treating a wider tolerance as an automatic fix. Minimum output is a practical execution boundary: it lets users state what result they will accept, while leaving the market free to move and the transaction free to fail.