Rango Bridge quotes can expire five minutes after retrieval, but the estimated output and preferred route may change sooner as liquidity, gas prices and bridge capacity move. To choose a route in Rango Bridge, refresh the quote immediately before approval and compare its new minimum received and fees. A Rango cross-chain swap proceeds on the transaction details returned at confirmation, not the earlier preview.
Three points matter most when comparing routes:
- A valid quote is still a snapshot, not a price lock.
- Compare destination output and wallet-paid gas separately.
- A failed final swap can leave you holding an intermediate token.
Rango Bridge searches integrated DEXs and bridges for a path, then estimates what each step will return. When you confirm, transaction creation checks the route again. The selected path can change even if the original quote has not expired.
A fee deducted from output is already reflected in the estimated destination amount; source-chain gas usually requires native tokens in your wallet. Subtracting an output fee twice makes a route look worse than it is. Ignoring separately funded gas makes it look cheaper than it is.
On a route that swaps, bridges, then swaps again, each step has its own execution risk. If the bridge succeeds but the destination swap fails, the resulting asset may be the bridged intermediate token. Check the received asset before attempting a fresh route.
Why can a quoted route change before signing?
A quoted route changes because its DEX prices, bridge liquidity and network fee estimates are sampled before the transaction is built. A pool trade can move the exchange rate; a bridge can change its available capacity or fee; and a new gas estimate can alter which path offers the best net result. The Rango routing algorithm may therefore select different steps for the same input amount.
The five-minute API expiry is an outer limit for creating a transaction from a quote, not a promise that its output holds for five minutes. Rango’s API troubleshooting reference recommends transaction creation within one minute because rates fluctuate. An approval transaction can consume part of that window, so refresh after approval if the displayed route is stale.
Route selection also depends on parameters that are easy to overlook: the exact token contract, source and destination chains, amount, selected wallets and slippage tolerance. Changing any of them can change the eligible swappers or return no route. A token symbol alone is insufficient when the same symbol exists on several chains or contracts.
Which route fields decide the actual cost?
Compare estimated output, fee funding, minimum received, input limits and route length together. A direct bridge may have fewer transactions, while a DEX–bridge–DEX path may deliver more of the requested token. The fastest or largest displayed output is not automatically the cheapest executable path.
Read each fee by where it is paid. Rango’s fee documentation distinguishes fees taken from the source wallet, deducted from output and, on some claim routes, paid from the destination wallet. Underlying swappers can charge their own fees. The direct app describes no extra app fee, while API integrations may add protocol or affiliate percentages; use the fee breakdown on the route you are actually signing.
For example, say two routes turn $10,000 of a stablecoin into the same destination stablecoin. Route A estimates $9,988 out and $7 of separately paid gas; route B estimates $9,978 out and $1 of gas. Their approximate economic results are $9,981 and $9,977, respectively, before any later price movement. Looking only at gas would reverse the choice.
Slippage tolerance is a constraint, not an extra fee. Rango’s API defaults to 0.5% if none is supplied, but the relevant check is the transaction’s current minimum received and the tolerance applied across its steps. Also inspect the route’s minimum and maximum input: bridge limits can invalidate an otherwise attractive quote for your amount.
What should you do when the quote changes?
Requote with the exact assets, amount and wallet addresses, then compare the fresh route against a minimum outcome you set in advance. Inspect the source and destination token contracts, intermediate asset, bridge step, estimated time and every fee line. If a changed route falls below your threshold, change the amount or wait for a better quote rather than widening slippage automatically.
A common mistake is to approve a token while viewing a good quote, then sign the later swap without checking its updated output. The fix is to compare the transaction creation result with the quote you accepted, including minimum received and fee funding. Rango’s single-step API flow explicitly allows an integrator to stop or request another confirmation when the new output is lower.
Keep enough native token for the source transaction and any later user-signed step. A Rango Exchange bridge route that requires a destination claim may need gas there as well. For a multi-step route, treat each completed step as a new starting position: the next quote must use the asset and amount actually received, which may differ from the initial estimate.
What else determines whether a route fits?
Timing, supported asset pairs, token conversion and failure handling determine whether a route fits after its price passes your test.
How long do transfers take?
Most supported swaps complete within a few minutes, but use the route’s estimated time as a comparison, not a deadline. Rango’s route data reports estimated seconds for each step; an example route in its API documentation shows 120 seconds. Source confirmations, bridge settlement, destination congestion and any claim transaction can extend the total into tens of minutes.
Which blockchains are supported?
Support spans EVM and non-EVM networks, including Ethereum, Solana, Bitcoin and Cosmos-based chains. That does not mean every token pair has a route: the selected bridge must support the asset and chains, and the amount must fit its limits. Check the live route results for your exact contracts; an absent route is more useful evidence than a general chain list.
Is the route safe to use?
No quote removes contract, bridge, approval or execution risk. Before signing, check the spender and allowance, the destination address, the bridge’s custody or liquidity model and the minimum received. If a step fails, inspect transaction status and the asset actually returned; it may be the input token or an intermediate asset on either chain, rather than the intended output.
Can tokens be swapped while bridging?
Yes. A route can swap the input into a bridgeable asset, transfer it, then swap it into the requested destination token. This expands the available pairs but adds DEX price impact, fees and a possible failure at the final leg. Compare that result with a route that bridges the desired token directly whenever both are offered.