Why Cross-Chain Routes Set Different Minimums

Cross-chain routes have different minimums because each route must cover its own execution costs and meet its own liquidity and protocol rules. A route may combine a source-chain swap, a bridge or solver transfer, and a destination-chain swap; another route may use different components or skip a swap. Its minimum is the lowest input those components can process under their current conditions.

That threshold is a route constraint, not a universal rule for moving tokens between chains. For a fuller account of how Fermi Swap moves tokens across chains, see the linked explainer. The route shown for a transfer is the useful unit of comparison: changing the destination token, network, or execution path can change the minimum.

What costs set a route’s minimum?

Fixed execution costs matter most when the transfer is small. A route may need a relayer or solver to pay transaction costs on the destination chain, while the user pays on the source chain. Some systems account for these costs through a fixed fee or a minimum charge. If the expected fee consumes too much of a small transfer, the route may reject it or quote a higher minimum.

Variable costs also differ. A percentage fee scales with the input amount, while a fixed fee does not. Swaps can add pool fees and price impact. The route may need enough value left after those deductions to complete each step and deliver a usable destination amount. Token decimals and contract rules can also prevent very small amounts from being represented or processed.

How does liquidity change the threshold?

Liquidity determines how much a route can trade at a tolerable price. A pool with limited depth may produce severe price impact for a modest swap; a bridge or solver may also have limited available inventory for a particular asset and direction. A router can therefore set or calculate a minimum for that path, even when another path between the same chains accepts less.

Route minimums can also change over time. Fees, liquidity, and the available execution paths can shift. A quote that worked earlier may no longer be available when the transaction is submitted. The route provider may return a new quote, reject the transfer, or require a different path. A displayed minimum is a condition for that quote, not a promise that the route will remain available.

What should you compare before sending?

Check the amount the route requires you to enter separately from the minimum output it promises to accept. The first is an input threshold. The second is usually a slippage bound: execution fails if the delivered amount falls below it. They protect against different problems and should not be treated as interchangeable.

Compare the route’s expected output and total cost, including both networks’ execution costs and any swap or bridge fees. A lower input minimum does not mean a cheaper transfer or a better exchange rate. For a small amount, a fixed fee can dominate; for a larger amount, price impact or a percentage fee may matter more.

• Confirm the source and destination networks, tokens, and direction.
• Read the input minimum, expected output, fees, and minimum output as separate fields.
• Refresh the quote before signing if the displayed route or conditions have changed.
• If the amount is below the minimum, compare another route or wait for conditions to change; do not assume splitting it will help, since fixed costs may apply to each transfer.

The better route is the one whose full quote fits the amount and output you need. Minimums describe what a route can execute under its stated conditions; they do not, by themselves, measure its value or reliability.