Compare Swap Routes by What Arrives, Not the Quote

To compare swap routes, measure what each route is expected to deliver after its costs, using the same input, destination asset and execution conditions. A route can show a larger quoted output and still leave you worse off if it adds fees elsewhere or needs more network gas. Start with the amount you send, then trace each deduction to the amount you can use at the end.

What does a swap route’s quoted output include?

A quoted output is an estimate of how much of the destination token you receive for a specified input. In a direct swap, the trade passes through one liquidity pool. A multi-hop route trades through two or more pools, often using an intermediate token. Each pool applies its own fee, and the size of the trade relative to available liquidity affects the exchange rate, a cost called price impact.

Route aggregators may compare several paths and display the estimated output after pool fees and price impact. Other costs can sit outside that number. Network gas pays for the transaction, and a cross-chain route can also involve a source-chain swap, a transfer between chains and a destination-chain swap. Those steps may have separate fees or different delivery conditions. For cross-chain routing, the fuller thor swap guide explains why the destination chain belongs in the same comparison. Check which costs the quote includes before treating its output as net.

How do you compare routes on the same basis?

Hold the input amount and destination token constant, then compare estimates made for the same execution window. A route with fewer hops is not automatically better: it may have less liquidity and a worse exchange rate. The useful comparison is the estimated result after each route’s costs, not the number of steps in its path.

Separate costs by what they reduce. Pool fees and price impact normally show up in the estimated token output. Gas may be charged in a different token, and a bridge or service fee may also be deducted separately. If your goal is to receive as many destination tokens as possible, compare the expected token amount and list other costs alongside it. If your goal is the best economic value, convert separately paid costs into a common unit using the same reference price for every route.

• Use the same input amount, source asset and destination token.
• Check whether the displayed output already reflects pool fees and price impact.
• Add separately charged network, transfer or service costs to the comparison.
• Compare the same execution window and destination conditions.

This is like comparing the total price of two journeys: the fare matters, but so do charges paid along the way. Keep the accounting consistent, and a route with a slightly lower token quote may still be preferable if its other costs are lower.

Why can the final amount differ from the estimate?

A quote describes expected execution, not a guaranteed delivery. Between quote and transaction, the pool price can move or available liquidity can change. Slippage is the difference between the expected exchange rate and the rate at execution. A transaction’s slippage setting limits how much the rate can move before the swap fails; a tighter limit can reduce unwanted price movement but makes a failed transaction more likely if the market moves.

Cross-chain routes add timing and destination steps. The source transaction may succeed while the destination swap or delivery takes longer, and the amount received can depend on the conditions when that later step executes. Read the route’s minimum-output figure, if provided, alongside its estimate. Also check which chain receives the asset and whether the quoted destination token is the one you intend to hold.

For most comparisons, choose the route with the strongest expected net result after costs, provided its minimum output and destination match your needs. Recheck the quote just before signing: the amounts and conditions can change. What changes the decision is the final usable output, and the next thing to watch is whether the transaction executes within the route’s stated limits.