Cross-Chain Swap Slippage: What Minimum Output Protects

Minimum output sets the least amount of the destination token a cross-chain swap may deliver before its swap contract rejects execution. It is a limit on the result, not a promise that the route will complete or that the source-chain transaction can be undone. The distinction matters because a route can contain separate source swap, bridge, and destination swap operations, each with its own execution conditions.

What does minimum output mean in a cross-chain swap?

Minimum output is the amount of the final token the route must deliver for the destination swap to count as successful. In a conventional exact-input swap, the trader fixes the input and accepts a variable output; a router checks that the output meets its amountOutMin threshold. If it does not, that on-chain swap reverts.

A quote gives an expected output at a particular point in time. A slippage tolerance allows execution to produce less than that quote, usually by defining a floor: quoted output multiplied by one minus the tolerance. The floor is denominated in the output token’s smallest units. It does not change the quote, reserve state, or exchange rate; it changes what result the contract is allowed to accept.

In a cross-chain route, “minimum output” can refer to a floor for the final destination token or a threshold on an intermediate leg. Those are different checks. A route may first swap on the source chain, bridge the resulting asset, then swap again on the destination chain. Each swap can move against the quote independently. For a fuller look at the contract sequence, see this guide to building a Biswap cross-chain swap flow. The key question when reading any route is which contract checks which amount, and at what stage.

Where does slippage enter the route?

Slippage enters wherever the route trades against a changing price or a quote that can change before execution. In an AMM, the swap itself moves the pool price; larger trades against thinner liquidity generally have greater price impact. Between quoting and execution, other trades can also change reserves. A route that swaps on both chains has two market-sensitive legs.

Bridge fees, protocol fees, and token conversion costs also affect the amount that reaches the next step, but they are not all “slippage.” A quote may already account for some costs. Applying an additional blanket deduction to a quoted minimum can therefore make the route unnecessarily strict. Conversely, treating a fee estimate as a guarantee can leave too little output for the destination swap.

When an API accepts a “min output” trade type, that may mean the requested destination amount is the constraint and the service calculates the input needed. That is distinct from exact-input trading, where the user fixes the source amount and accepts a variable destination result above a floor. Check the route’s terms and calldata: the interface label alone does not tell you whether tolerance is applied to one swap, split across two swaps, or enforced as a final output condition.

What happens if the route misses its minimum?

The contract that enforces the threshold determines the failure behavior. If a destination swap checks its received output against a minimum and falls short, that swap can revert. But an asynchronous cross-chain route is not one atomic transaction: the source transaction may already have completed before the destination execution is attempted. Its effects cannot generally be erased by a later destination-chain revert.

Protocols handle this failure differently. A route may leave the bridged asset available for retry, send it to a specified refund address, or require a separate recovery action. The exact outcome depends on the route’s contracts and failure handling. A failed destination swap does not by itself establish that the source funds were lost, nor does it guarantee that a refund will be automatic.

Before signing, inspect the route’s expected output, minimum output, recipient, and any stated refund or recovery path. Confirm that the minimum is expressed in the final token you intend to receive, not an intermediate bridge asset. Also check whether changing the tolerance changes only the destination swap’s guard or affects other legs. A lower minimum makes execution easier under adverse price movement but accepts a worse result; a higher one protects the quoted result more tightly but increases the chance of a revert or delayed completion.

How should you choose a minimum output?

Choose a floor from the route’s current quote and the loss you are willing to accept, then verify where that floor is enforced. The most useful comparison is between the expected final balance and the minimum final balance after the route’s fees and conversions—not between the source amount and a headline exchange rate.

• Read the final token and chain from the route, then check the minimum in that token’s units.
• Find out whether the quote’s fees are already included before applying any additional tolerance.
• For multi-leg routes, identify the threshold on each swap and whether the final destination amount has its own check.
• Review the documented retry, refund, or recovery behavior for destination execution failure.

A tight floor is useful when preserving a price matters more than immediate completion. A looser floor is useful when completing the route matters more than limiting the price difference. Neither setting protects against every route risk: the check covers only the amount and execution point its contract actually tests.

Confirmed by the transaction data and route definition are the quoted output, the encoded minimum, and the contract that enforces it. Whether a failed destination leg will be retried, refunded, or need recovery remains route-specific and should be verified before sending.