DEV Community

Gideon Elliott
Gideon Elliott

Posted on

Why Does My Cross-Chain Quote Differ From the Final Amount?

A cross-chain quote is an estimate of what the destination transaction can deliver under current prices and fees; the final amount is what settles after execution. They differ when prices move, liquidity changes, or fees are charged separately or recalculated. For treasury planning, compare the quote, minimum-output condition, and settled balance as distinct figures.

A quote estimates a route, while settlement records execution

A cross-chain route can combine a source-chain transfer, a bridge or relayer charge, a destination-chain swap, and destination gas. The quote estimates these legs using current liquidity and fee data; settlement occurs later, sometimes after source-chain confirmation or a relayer fill. The longer that gap, the more opportunity for market prices and execution costs to change.

If your treasury needs to transfer one asset and receive another in a single cross-chain flow, a relay bridge service can route the transfer and swap together. Read its quoted output as an estimate for that route, then check which costs are deducted from the received amount and which are paid separately.

For an on-chain swap, pool price impact depends on trade size relative to available liquidity; the Uniswap documentation describes this relationship for automated market makers. A cross-chain quote can also include a relayer’s charge for destination-chain gas, capital, and execution risk. The Ethereum gas documentation explains why destination computation has a separate cost: transactions pay for the resources they consume.

Fees and price movement affect the amount in different ways

Separate explicit deductions from execution-price changes. A bridge or relayer fee may be deducted from the input or output, while a swap’s pool fee is reflected in its execution. Gas may be paid from a separate native-token balance, included in a relayer’s quoted cost, or deducted from output, depending on the route.

Price impact is the trade’s effect on the pool price; slippage is the difference between expected and actual execution, including intervening market movement. A quote can estimate both, but a slippage tolerance usually sets a minimum acceptable output rather than promising that exact amount. If the result falls below that minimum, the destination swap may revert, even though the source transaction has already finalized.

On liquid major-token routes, teams commonly consider a tolerance around 0.1–0.5%; thinner pools or volatile assets may need more. That extra tolerance allows a worse execution price, so it should not be increased just to force a transaction through. Set it from observed volatility and trade size, and use a stricter limit when a minimum payout matters more than completion speed.

A worked example separates estimate from minimum

Suppose a route quotes 10,000 USDC in for an estimated 9,970 units of a destination token after expected charges and swap pricing. With a 0.5% tolerance, the minimum acceptable output is 9,920.15 tokens. If execution delivers 9,948, the transaction succeeds: the difference from the quote is 22 tokens, or about 0.22%.

The 22-token gap is not automatically a hidden fee. It could result from the destination pool moving before execution or from execution at a slightly worse price than estimated; the fee breakdown and transaction records show which costs were actually charged. If output falls below 9,920.15, the swap may fail its minimum-output check instead of settling at that lower amount.

Treasury controls should use settled amounts

For recurring transfers or payouts, budget against the minimum output when the route exposes one, and reconcile against the destination-chain balance after settlement. Record input amount, quoted output, minimum output, actual output, and separately paid gas; this makes route performance comparable across transfers even when token prices change.

When a quote expires or the market moves before execution, refresh it and reassess the minimum before submitting. For relay bridge transfers, I would size batches against the destination amount the business must receive, then split or delay a transfer if the available quote cannot meet that requirement within the approved tolerance.

Top comments (0)