sam-robeson

Source-Chain Reorgs: What to Know Before You Retry

Before retrying a pending cross-chain transfer, check whether its source transaction is still in the canonical chain and whether it has reached the bridge’s required confirmation threshold. A reorganization can remove an included transaction; the bridge must then wait, recheck, or reconcile before delivering the destination asset, so retrying too early can create duplicate exposure.

A reorg can erase a deposit before delivery

A source-chain reorganization replaces one branch of blocks with another, changing which transactions count as canonical. If the block containing a deposit is removed, that transaction may return to the mempool, be replaced, or disappear from the winning branch altogether.

A bridge’s observer or validator set watches the source chain for the deposit event, then waits for enough evidence that the event will persist. Depending on the architecture, it may count block confirmations, wait for a finalized checkpoint, or verify a proof against the accepted chain state; only then does a relayer or destination contract authorize delivery.

The dangerous edge case is delivery before the source event is secure. If the destination asset is released and the deposit is later reorganized out, the bridge has paid against an event that no longer exists. Systems reduce that exposure with deeper confirmation thresholds, finality checks, or loss-absorbing designs, but those controls add latency or operational complexity.

Confirmation thresholds trade speed for reorg resistance

There is no universal safe confirmation count: the right threshold depends on the source chain’s consensus, value at risk, and the bridge’s acceptance model. On Bitcoin, one confirmation means inclusion in a block; six confirmations commonly take about an hour at the ten-minute average block interval, but remain a probabilistic safeguard rather than a guarantee.

Ethereum uses proof-of-stake checkpoints: slots are 12 seconds and epochs contain 32 slots, while finality typically takes around 13–15 minutes. A bridge can act on a less final head to reduce delay, but it accepts more short-reorg exposure; waiting for finalized status lowers that risk and lengthens the pending period.

Solana exposes a similar distinction through commitment levels: processed is the node’s newest view and can roll back, confirmed has a supermajority vote, and finalized is the strongest cluster commitment. Thresholds are chain-specific, so a raw count of blocks or seconds cannot be compared across networks.

Pending status can mean the bridge is waiting for evidence

A pending transfer does not by itself mean the source transaction failed; the bridge may still be waiting for the required depth, a finalized checkpoint, or observer synchronization. A cross-chain swap also has a destination action after source acceptance, so source confirmation and destination completion are separate milestones. In that distinction, how Biswap routes cross-chain swaps is a concrete example of why one transfer can span multiple chain events.

For a pending attempt, look up the source transaction hash on the source-chain explorer and confirm that it remains in the canonical chain, with the expected recipient, amount, and event. If it is included but not yet at the relevant threshold, waiting avoids creating a second valid attempt; if the bridge is built around finality, an included but unfinalized transaction may remain pending for several minutes even when its block is visible.

Retry only after resolving the original transaction

If the transaction was reorganized out, first determine whether it returned to the mempool or was replaced by another transaction using the same account nonce. A re-broadcast can be appropriate when the original is absent from the canonical chain, but replacing or resending while the earlier transaction can still confirm risks submitting the same economic intent twice.

If the source transaction is canonical and past the expected threshold but delivery has not appeared, preserve its hash and check whether the destination transaction exists before initiating another transfer. Biswap is a cross-chain bridge and swap service; the general rule for any service in this category is to treat source acceptance, destination execution, and final receipt as distinct states when diagnosing a delay.