Why Cross-Chain Route Types Change Your Minimum

A cross-chain route changes what “minimum received” can mean because a transfer can swap tokens before a bridge, after it, or on both sides. The source transaction may enforce a minimum for the asset it sends, while the amount delivered on the destination chain depends on bridge fees, execution conditions and any destination swap. A quoted final amount is useful only if you know which of those legs has an enforceable bound.

That distinction matters when comparing routes that start with the same token and end with the same token. A route with a better quoted output can still expose more of the result to execution after the source transaction. For a fuller account of the business flow, see ParaSwap’s guide to business cross-chain transfers. The key question for any route is where its minimum is checked and what happens if a later leg cannot meet it.

How does a swap-before-bridge route set its minimum?

A swap-before-bridge route converts the source token into the bridge’s input asset on the source chain, then sends that asset across. Its first minimum is normally attached to the source-chain swap: the swap must return at least the specified amount of the bridge asset or revert. That protects the conversion before the transfer begins.

The minimum for that swap is not automatically a minimum for the user’s final destination token. The bridge may deduct a fee, use a destination-side representation of the asset, or deliver an amount that differs from the quoted estimate. If the route ends with the bridge asset, the bridge’s delivery terms define what is promised. If another swap is needed to reach the requested destination token, that later leg needs its own execution condition.

This route is useful when the bridge accepts a different asset from the one the user holds. It can also avoid relying on destination-chain liquidity for a final conversion. The trade-off is that source-chain swap slippage and bridge costs both reduce the amount that can arrive. A source transaction that succeeds does not, by itself, prove that a destination token minimum was met.

What changes when the swap happens after the bridge?

A bridge-before-swap route transfers an asset first and swaps it on the destination chain. The source transaction commits to the bridge transfer, while the destination swap determines how much of the requested token the recipient gets. A destination swap’s minimum output can constrain that final conversion, but only if the route executes that swap with an on-chain condition that reverts or otherwise handles output below the bound.

Until the transfer is available on the destination chain, the quoted swap is an estimate. Destination liquidity can change during that delay, and a route that cannot execute at its minimum may leave the user holding the bridged asset instead of the requested token. The route’s failure handling matters: does the destination swap retry, revert, or return the intermediate asset? Those outcomes are distinct from a source-chain swap reverting before funds leave the origin.

This structure can be preferable when the destination chain has better liquidity for the final pair, or when the bridge supports the asset the user already holds. It also shifts more execution risk to the destination leg. Check whether the quote’s minimum refers to bridge delivery or final swap output; the two values protect different stages.

Why use a swap on both sides of the bridge?

A composed route swaps into the bridge asset on the source chain, bridges that asset, then swaps again on the destination chain. It can connect a source token and destination token when neither is directly supported by the bridge. Its final minimum depends on the destination swap, while the source swap has a separate minimum and the bridge sits between them.

Each leg can pass its own check and the overall result can still be lower than an earlier estimate. For example, the source swap may produce an amount just above its minimum, then bridge fees reduce the deliverable balance, leaving less input for the destination swap. If the destination swap enforces a minimum, it can fail rather than return too little. Without such enforcement, the final output may fall below the quoted figure.

Compare routes by tracing the asset and bound at every step:

• Source swap: identify the output token and the minimum amount accepted before bridging.
• Bridge: check which token is sent, which token is delivered, and how fees or failed delivery are handled.
• Destination swap: confirm whether the minimum applies to the final token and what happens when the swap cannot meet it.

For most users, the better route is the one with an enforceable minimum on the final token and clear handling for a failed later leg, even if its displayed estimate is slightly lower. When comparing a Paraswap quote or another router’s quote, do not treat a source-side minimum as a guarantee of destination output. The route’s execution order determines which amount is protected and when.