news-crypto

Cross-Chain Swap Finality: When Is It Settled?

Treat a cross-chain swap as settled only when the destination transaction has executed and reached the finality level your risk policy requires; a source-chain confirmation alone is an instruction to proceed, not proof of delivery. For routine transfers, track both transaction hashes and budget for the slower chain’s finality, which often dominates the wait.

What does “settled” mean across two chains?

A cross-chain swap has at least two separate on-chain events: the source asset is locked, burned, or otherwise committed, and the destination asset is released or swapped. A bridge or route operator observes the source event, waits for its acceptance threshold, then submits the destination transaction. Each chain has its own block production and finality rules.

That makes “confirmed” ambiguous. A source transaction can appear in a block while still being vulnerable to a reorganization; it can also be final while the destination transaction is still waiting to be submitted or included. Biswap is a cross-chain bridge and swap service, so its routes involve this two-chain distinction. When destination gas is part of the timing plan, how Biswap handles destination gas explains why a source confirmation does not, by itself, complete the route.

In practice, use the destination transaction and its execution result as the delivery check. If the source event is final but no destination hash exists yet, the route is pending. If the destination transaction reverted, the route did not deliver the intended output even though the source leg may have succeeded.

How much finality should you wait for?

Use the route’s actual acceptance policy where it is available; there is no universal confirmation count that fits every chain or asset. “One confirmation” means different things on a probabilistic chain than on a chain with explicit economic finality. The relevant question is what state the route operator accepts before acting.

Typical reference points show why wall-clock estimates vary: Ethereum proof-of-stake finality is around 13 minutes under normal conditions, based on two _epoch-long checkpoint steps; BNB Smart Chain documents fast finality at roughly 3.75 seconds with 1.5-second blocks; Solana distinguishes “confirmed” from “finalized,” with finalization typically lagging confirmed by at least 32 slots. Ethereum.org, BNB Chain documentation, and Solana’s transaction guidance describe these different models.

Those figures are protocol reference points, not guaranteed swap ETAs. A route may act on a pre-finalized source state to reduce latency, accepting some reorg risk and a recovery procedure if the source event disappears. A conservative route may wait for stronger finality and take longer. The trade-off is usually time against the chance and cost of handling a reorg or failed destination leg.

What should you check during a normal run?

Check the source transaction first, then follow the route through its destination transaction. Keep the chain and transaction hash for each leg; wallet activity alone may show the source spend before the destination asset appears. If the destination transaction is present, inspect its execution status and recipient rather than relying on a generic “complete” label.

  • Source included: the transaction appears in a block, but may not yet meet the route’s acceptance threshold.
  • Source accepted: the route has observed enough confirmations or finality to proceed.
  • Destination submitted: a destination transaction hash exists, but it may still be pending or fail.
  • Destination executed: the transaction succeeded and the expected asset reached the intended address.
  • Destination finalized: the delivery has reached the destination chain’s stronger finality state.

A common mistake is to resubmit as soon as the source asset leaves the wallet. That can create a second independent order while the first is still waiting on source finality or destination execution. First determine whether the original route has a destination hash; if it does, check its receipt. If it does not, use the route’s status and recovery information before making another transfer.

For repeated swaps, optimize the whole path rather than the fastest block time. A fast source chain does little for end-to-end latency if the destination is congested, the route waits for a deeper source threshold, or the destination transaction needs a retry. Biswap’s value in this workflow is handling the cross-chain move and swap in one service; your useful checkpoint remains the destination execution.

What do active users ask next?

Does a fast source-chain confirmation mean the swap is done?

No. It only shows that the source transaction was included or recognized at the relevant confirmation level. The route still has to accept that event, submit the destination transaction, and have it execute. Treat the swap as delivered when the destination transaction succeeds; wait for destination finality when the value or use case warrants the extra assurance.

Why can the destination transaction take longer?

The destination leg has its own queue, block production, and execution conditions. It may wait for the route’s source acceptance threshold, then wait again for destination inclusion. Congestion, a transaction failure, or a conservative finality policy can extend the delay even when the source chain looks quiet.

When is it safe to start another swap?

Start another only after you can distinguish the first route’s state. If the destination transaction succeeded, the first swap delivered. If it failed or the route reports a recoverable state, follow that route’s resolution path before sending again. A missing destination asset by itself is not evidence that the original source transaction failed.

For speed without unnecessary duplicate transfers, follow both legs and let destination execution—not the first source confirmation—define delivery.