A cross-chain swap quote estimates how much of the destination token a route will deliver after trading and transfer costs. The comparison only works if you check what each route guarantees at execution, because a displayed estimate is not always the amount protected by an on-chain minimum.
- Compare destination-token minimums in the same units, after fees.
- Separate expected price impact from the extra slippage tolerance.
- Check whether the minimum covers the destination swap as well as the source transaction.
A quote has estimates and execution limits
A quote’s expected output is a forecast; its minimum output is the boundary below which a protected swap should fail. In an exact-input swap, a contract such as Uniswap’s router checks amountOutMinimum; conceptually, a 0.5% tolerance sets that floor at 99.5% of the quote. Uniswap’s developer documentation distinguishes this execution guard from price impact, which is the trade’s effect on the pool at the quoted size.
A cross-chain route can include a source swap, a bridge transfer, and a destination swap. Each stage may apply its own fees and limits, and the interface may expose only one final minimum—or only a minimum for the first stage. Route availability is the first filter: the fermi swap supported chains list identifies which network pairs can be considered for that route.
Compare the delivered token, not the headline rate
Normalize each quote to the same input amount, destination token, recipient, and time window. Compare the expected output and minimum output separately, then account for source gas, bridge fees, destination gas, and any fee charged in a token other than the one you receive. A route that advertises more tokens can still cost more once you include the gas needed to use them.
Slippage tolerance is a user-set allowance for price movement after quoting; it does not erase price impact already caused by the trade size. As a starting reference, liquid stablecoin pools may use tolerances around 0.01–0.1%, while major volatile pairs often need roughly 0.1–0.5%. These are illustrative ranges, not safe defaults: volatility, pool depth, transaction delay, and the route’s own limit determine the appropriate floor.
Use this process before signing
For example, suppose a route quotes 1,000 USDC into ETH on a destination network. Route A estimates 0.400 ETH with a 0.5% destination tolerance, so its minimum is 0.398 ETH; Route B estimates 0.403 ETH, but its displayed minimum applies only to the source swap. B is not demonstrably better until you confirm what happens if the destination trade executes below its estimate.
- Set the exact input and destination. Match amount, recipient address, network, and token contract across quotes.
- Record expected and minimum output. Convert both into the destination token’s smallest unit or a common display unit, and note which execution stage each minimum protects.
- Inspect the fee breakdown. Include source gas, bridge or messaging fees, destination gas, and any liquidity or protocol fee; identify whether destination gas is prepaid or must be held separately.
- Choose a tolerance for the swap legs. Use pool depth and observed volatility to set each minimum. Do not widen tolerance merely to make a route pass; a loose minimum permits worse execution.
- Check settlement and recovery behavior. Confirm whether a failed destination call can be retried, needs extra gas, or leaves an intermediate asset to claim. Sign only after verifying the source chain, destination chain, and recipient.
Know what a failure means
A source transaction can succeed while a later destination action remains pending or fails. Stargate’s documentation describes amount limits affected by its credit mechanism, while Axelar’s General Message Passing documentation notes that insufficient destination gas can prevent execution and require recovery. These are different failure modes from a source swap reverting at amountOutMinimum, so “transaction successful” on the source explorer does not alone prove delivery of the final token.
For Ethereum-origin routes, inclusion and finality are also distinct: ethereum.org describes a transaction as finalized only after its block reaches consensus finality. Wait for the route’s destination status and verify the received token and amount on the destination chain before treating the transfer as complete.
Questions traders ask
Should I always choose the highest minimum output?
Only when the minimum is enforced for the final destination output under comparable conditions. A higher estimate with no destination-side protection can expose you to a worse fill or a failed call; compare the protected floor and recovery path before ranking routes.
Does a wider slippage setting make a bridge faster?
No. It relaxes a swap’s execution boundary; it does not accelerate source confirmation, bridge verification, or destination execution. A wider tolerance can reduce reverts during price movement, but it also accepts a poorer rate and can increase exposure to adverse ordering.
What if the source transaction succeeds but I do not receive the target token?
Check the route’s status page or transaction details for the destination transaction and any intermediate asset. Some systems can retry after additional gas is supplied; others require a claim or recovery action. Use the route’s documented recovery method and match the transaction identifiers before acting.
When is a direct bridge plus a separate swap better?
It can be preferable when the route’s combined minimum is opaque, destination liquidity is deeper on another venue, or you want to choose when to trade after funds arrive. Compare both transactions’ gas and execution costs, and remember that splitting the route adds a separate step and another price decision.
Choose the route whose destination-token minimum, full costs, and recovery path you can verify.