Choose Cross-Chain Routes by What Arrives on the Destination

Choose a cross-chain route by comparing how many usable tokens it is expected to deliver on the destination chain after fees and price impact. A route can swap your token before the bridge, transfer it across, then swap it again into the token you need. Each step uses different liquidity, so the largest bridge or the lowest advertised fee alone may not make the best route.

Start with the destination token and the amount you intend to move. A route finder can return several combinations of swaps and bridges. LI.FI’s quote API describes routes as steps, including single-chain swaps and cross-chain transfers, and provides estimated output amounts. For the interface sequence, see QuickSwap’s first cross-chain swap steps; the route choice itself depends on the quote for your amount and destination.

What does destination liquidity tell you?

Destination liquidity tells you whether there is enough trading depth to convert the bridged asset into the token you want at a reasonable price. If the bridge delivers the exact token you need, destination swap liquidity may not matter. If it delivers a different token, the final swap depends on pools or market makers on that chain.

A pool is like a market stall with a small shelf: a large order takes more of what is available and pushes the price against you. In an automated market maker, the balance of tokens in the pool determines the exchange rate. The larger your trade relative to that pool, the greater its price impact may be. A route’s estimate should account for this expected conversion, but the pool can change before your transaction executes.

Check whether the displayed output is the amount before or after the destination swap. Also check whether it is an estimate or a minimum amount enforced at execution. A route that bridges quickly but leaves you with a thinly traded intermediate token may be less useful than one with a slower transfer and a deeper final market.

How should you compare route quotes?

Compare the same input amount, source token, destination chain and final token across routes. Focus on the amount you expect to receive after all route costs, then check the assumptions behind that number. A practical comparison includes:

• Final output: the estimated amount of the token you actually want, after any destination swap.
• Price impact and minimum received: the quote’s expected effect on price and the execution limit that protects against a worse fill.
• Fees and gas: bridge or relayer fees, swap fees and network costs. Across’s fee documentation, for example, separates liquidity-provider and relayer fees, and says its LP fees vary with pool utilization and route.
• Execution time and steps: how long the bridge expects to take, whether a separate destination transaction is needed, and whether you must have gas on that chain.

Do not compare a bridge fee in isolation. One route may charge less to transfer the asset but require a costly or price-sensitive swap at the other end. Another may charge more upfront yet deliver more of the desired token overall. Fresh quotes matter: Across notes that its fees change with market conditions, pool utilization and gas prices, while a destination swap’s pool balance can also move.

When should you avoid the highest-output route?

Choose the highest-output route only when its estimate is credible for your trade size and its execution conditions suit you. A quoted amount can change while the source transaction is pending. The route may fail if the final swap falls below its minimum output, and the displayed estimate does not make the destination pool’s liquidity permanent.

For a small transfer, a minor output difference may be outweighed by an extra transaction or a long delay. For a larger transfer, pay closer attention to price impact and whether the final pool can absorb the trade without a sharp price move. If the quote hides price impact or does not show a minimum received amount, compare another route or reduce the amount.

Before signing, confirm the destination chain, token contract, recipient address and final minimum output. If you need a token that is thinly traded on the destination chain, test a smaller amount first. The best route is the one that leaves you with the most usable destination tokens at an acceptable execution risk, not simply the route with the shortest bridge path.