The floor beneath a cross-chain swap quote

A cross-chain swap’s minimum received amount is the lowest output the route is allowed to deliver under the quote’s execution rules. It gives you a threshold for accepting price movement between the quote and completion. It does not guarantee that amount will arrive: the route can fail, or its terms may handle a failed step differently.

A route may swap tokens before bridging, then swap again on the destination chain. Each handoff can take time, and the token price, available liquidity and fees can change while it runs. The displayed estimate and the minimum therefore answer different questions: one is the expected result; the other is the floor the quote is willing to accept. The fuller bungee bridge guide traces the handoffs and checks in more detail.

What does minimum received mean on a cross-chain swap?

It sets the least output a route will accept, subject to how that service implements execution. A swap on an automated market maker typically uses a minimum output to limit slippage: if the trade would return less than the threshold, that swap can revert. Cross-chain routes add steps and chains, so the displayed minimum might refer to the final destination token, one swap within the route, or another stage. Check the quote’s explanation before signing.

This distinction matters because a cross-chain route is not always one indivisible transaction. The source-chain action might complete before a destination-chain swap runs. If a later step cannot meet its conditions, the outcome may depend on the route’s recovery or refund process. Read the route details for what happens after each step, rather than assuming the minimum is a promise of delivery.

Why does the minimum change between quotes?

The floor reflects the quote’s assumptions about price movement, fees and execution. A route with more swaps can expose the result to more price changes than a direct transfer, while a route through deeper liquidity may tolerate a larger trade with less price impact. Network fees can also affect the destination amount, depending on how the quote accounts for them.

Compare routes using the same starting amount and destination token. Then check:

• Whether the minimum refers to the token you expect to receive.
• Which fees are deducted before that amount is calculated.
• How long the quote remains valid and whether it refreshes before signing.
• What the route says will happen if a later step cannot execute.

A larger minimum protects more of the expected output, but it can make execution more likely to fail when prices move. A smaller minimum gives the route more room to complete, at the cost of accepting less. Changing the threshold does not improve the route’s price; it changes the result you are prepared to accept.

How should you choose a minimum received amount?

Start with the route’s quoted minimum and decide whether the output after fees is acceptable. If it is too low, compare another route or wait for a fresh quote before signing. Widening the tolerance may help a route complete during price movement, but it also permits a worse result. For most readers, the safer choice is to accept only a floor they would be comfortable receiving and let the route fail if it cannot meet that condition.

Watch the quote’s minimum, expiry and fee breakdown, then compare them with the destination amount shown at signing. After submission, check the source and destination transaction status and any recovery instructions if the route stops between chains. Those signals show whether the quote’s floor held and whether the transfer completed as planned.