Set a Minimum Receive Amount for Cross-Chain Swaps

A cross-chain minimum received amount sets the least destination token you agree to accept when a route moves and swaps tokens across networks. It gives you a clear limit if prices or fees change before the route finishes. The quote is an estimate; the minimum is the bound. For a fuller walkthrough of how a route can bridge and exchange tokens, see fermi swap.

What does minimum received protect?

It protects the output amount, but only where the route applies that bound. A cross-chain swap can involve a source-chain transfer, a bridge, and a destination-chain swap. Each step may use different contracts and price checks. The minimum might apply to the final token on the destination network, or only to one swap within the route.

Slippage is the difference between a quoted output and the output at execution. A route may also subtract bridge fees, swap fees, and destination gas costs. So a minimum shown for an intermediate token does not necessarily tell you what will arrive in your wallet. Check the token, network, and step named beside the minimum. If the screen does not make the final output clear, treat the figure as incomplete.

How should you calculate the bound?

Start with the route’s quoted amount for the exact token you want to receive, after expected fees. Then set the lowest amount you would still accept. A common calculation is quoted output multiplied by one minus the slippage tolerance. For example, a 1% tolerance on a quote of 100 destination tokens gives a 99-token minimum. The number is an example, not a suggested setting.

Use the whole route quote rather than applying the percentage to your input amount. Input and output tokens can have different prices, and bridge fees may be charged in another token or deducted along the way. Some routes calculate the minimum themselves; others expose a field or use separate bounds for separate swaps. Read the transaction details to see what the contract will enforce.

• Confirm the destination network and token contract, especially when token names look alike.
• Compare the estimated final amount with the minimum final amount, after route fees.
• Check whether the minimum covers the destination swap or only an earlier step.
• Review the route again before signing if the quote has expired or changed.

How tight should the minimum be?

A tighter bound means less room for the output to fall, but it can make a transaction fail when the route moves before execution. A looser bound gives the route more room to complete, while accepting a worse result. There is no universal percentage: liquid pairs and volatile pairs behave differently, and cross-chain delay can add another chance for conditions to shift.

Choose a minimum from the amount you can accept, not from a desire to make every route succeed. If the quote only works with a much lower minimum than you are comfortable with, wait for a fresh quote or choose a route whose final amount meets your needs. The useful check is simple: know which destination asset the bound covers, and know the least amount you would accept before you sign.