kendra-koepp

How to Vet a Cross-Chain Swap Route Before Signing

A cross-chain route can take seconds to minutes to settle, so check what must happen after your source transaction confirms before you sign. A “swap” may bundle a source-chain trade, a bridge message and a destination-chain trade, each with different failure conditions.

Three checks decide whether the route fits:

  • Identify what security assumption protects the bridge message.
  • Compare the destination amount with its minimum output and required gas.
  • Know how the route handles delayed or failed destination execution.

What does the route quote actually promise?

First separate the quoted amount from the route’s settlement guarantee. A quote usually estimates the destination asset after bridge costs, destination execution and any swaps; it does not mean the destination transaction has already happened. Check whether the route pays from destination liquidity immediately or waits for a message and its proof to be accepted.

In a message-based bridge, the source contract emits an event after locking or burning tokens. An attester set observes it, waits for the configured source finality, and signs a message; a relayer submits that proof to the destination contract, which releases or mints the asset. In Wormhole, for example, Guardians sign a VAA after reaching a two-thirds supermajority, while relayers deliver it; the relayer can affect timing, but cannot change the signed message.

Read the route’s finality setting where available. Wormhole distinguishes instant, safe and finalized: faster attestation reduces waiting but raises reorganization exposure. On BNB Smart Chain, block time is about 0.45 seconds and fast finality is typically reached in roughly two blocks when enough validators vote; a bridge may still wait longer to meet its own security policy. A chain’s confirmation time is only one part of end-to-end settlement.

How do you compare the destination outcome?

  1. Trace every leg. Write down the source token, intermediate representation, destination token and chains. Confirm that the bridge representation is the asset you intend to trade; a wrapped token and a native issuance can share a ticker while having different redemption and liquidity risks.
  2. Compare the minimum received. Use the destination transaction’s minOut or equivalent, not only the headline estimate. For example, if a route estimates 1,000 tokens with a 1% tolerance, a 990-token minimum may permit execution after adverse price movement; a wider tolerance lowers revert risk but accepts a worse fill. Check whether the quoted minimum applies after both bridge delivery and the destination swap.
  3. Check who supplies destination liquidity. A liquidity-funded route can deliver quickly because a provider pays out on the destination and later rebalances; its quote embeds inventory, hedging and rebalancing costs. A burn-and-mint or lock-and-release route may avoid that inventory premium, but waits on finality, attestation and destination execution. For a single-flow bridge and swap across networks, quickswap is relevant when you want the transfer and exchange handled together; compare its stated destination result with the route alternatives you are evaluating.
  4. Confirm gas and recovery conditions. Ensure the destination account can receive the asset and that the route funds destination gas or leaves you a way to pay it. If the source transaction succeeds but destination execution reverts, the bridge transfer may still be complete while the swap is not; check whether recovery means claiming the bridged asset, retrying execution or contacting an operator. Those are materially different outcomes.

What should you do if settlement stalls?

Track the source transaction hash first, then the bridge message or transfer identifier, then the destination transaction. A confirmed source transaction with no destination transaction points to attestation or delivery delay; a reverted destination transaction points to execution failure. Do not submit a second transfer just because the destination balance has not appeared: the first message may still be relayable, and a duplicate can leave you with two transfers.

My rule is to choose the route whose minimum destination output and recovery path you can explain before signing. Keep the message identifier and source hash, and use them to distinguish a slow relay from a failed swap; that distinction determines whether you wait, retry or claim the delivered asset.