Bridge Quote vs Settlement: Treasury Reconciliation

If your treasury needs a fixed amount on another chain, treat the route quote as an estimate and reconcile against destination settlement before marking the transfer complete. The quote describes an intended path and expected output; it does not prove that every cross-chain step executed. You can use the Rango bridge app to source a cross-chain route, then verify the outcome against the receiving chain.

rangobridge.com is Rango Exchange’s cross-chain DEX and bridge aggregator.

What does a quote prove, and what does settlement prove?

A quote proves that a route was calculable at a particular time using the balances, liquidity, and parameters available then. It commonly records the input amount, route legs, estimated output, minimum output after slippage, and a deadline or expiry. It is a pre-execution snapshot: it cannot guarantee that the source transaction will be included promptly or that destination execution will succeed.

Settlement proves that the intended asset arrived at the destination address and is spendable there. A route can involve source-chain token approval or transfer, a bridge message or packet, destination-chain execution, and a final swap. Each stage has its own transaction or protocol state. A successful source transaction alone proves only that the source-side action occurred.

Rango Bridge is relevant when you need to assemble a cross-chain route, but accounting should follow the resulting destination-chain state. For an Axelar General Message Passing route, for example, the source contract emits a call event and a relayer submits execution on the destination; for an IBC transfer, packet receipt and acknowledgement or timeout are distinct lifecycle events. In either case, an in-flight message is not yet usable treasury inventory.

How should you reconcile a transfer end to end?

Match the route’s source transaction hash to the sending address, source chain, token contract, and exact amount debited. Record the destination chain and recipient from the intended transfer, then follow the protocol message or packet identifier where available. Do not rely on a single status label: “confirmed” may describe source inclusion, while destination execution is still pending.

For example, suppose a treasury sends 10,000 USDC and the quote estimates 9,970 USDC after route costs, with a minimum output of 9,900 USDC. These are illustrative figures. After source confirmation, wait for the destination transaction to succeed, then check the recipient’s token balance and confirm the token contract is the intended USDC representation. Reconcile the actual received amount, not the quote estimate.

If destination execution includes a swap, compare actual output with the route’s minimum-output condition, not with the headline estimate. A revert may leave the bridge leg completed while the swap leg fails, depending on the route’s design. Treat that as an exception requiring state-by-state investigation; do not submit the original transfer again until you establish whether the first message can still execute.

Keep the source hash, destination hash, message or packet ID, quoted minimum output, and actual received amount together in the treasury record. If the destination is Cosmos Hub or another IBC chain, check the packet sequence and acknowledgement; a timeout is a separate outcome that may trigger a refund path. If destination execution is pending, leave the item in transit rather than booking it as available funds.

Can I book funds when the source transaction succeeds?

No. Source success establishes that the sending-chain transaction executed; it does not establish destination receipt or successful destination-side swaps. Keep the transfer in an in-transit account until the intended asset appears at the recipient address on the destination chain and meets your organization’s finality policy.

What if the destination amount is below the quote?

Compare the received amount with the quote’s minimum output and inspect each destination transaction for a swap, fee, or failed execution. If it is below the enforced minimum, investigate the route state before retrying. A displayed estimate can differ from actual output, but an enforced minimum should define the route’s execution boundary.

How long should I wait before treating a route as stuck?

Use the route’s protocol state and chain finality, not a universal timer. Ethereum finality is typically about 15 minutes, while other chains and relayers have different timing. If the source is final but no destination execution appears, track the message or packet; for IBC, check whether it was acknowledged or timed out.

Decision rule: book the transfer as complete only when the intended destination asset is confirmed at the intended address and the received amount satisfies your treasury’s minimum.