Jump to content
Crypto Front Page

Crypto networks, markets and policy

What Is Block Finality? Why Your Bridge Transfer Waits

Block finality is when a block can no longer be reversed. Bridges wait so a deposit cannot vanish after its funds are released on another chain.

The Crypto Front Page Desk4 min read

What Is Block Finality? Why Your Bridge Transfer Waits

Block finality is the point at which a block can no longer be reversed under a chain’s rules. A bridge waits for that point before releasing funds on another chain because a reorganization could erase a deposit after its payout has already gone through.

Say you send a deposit from Ethereum to another network. The transaction can appear in a block within about 12 seconds, and your wallet may show it as confirmed. But Ethereum proof of stake finalizes checkpoints through Casper FFG, usually after two epochs, or about 12.8 minutes. The bridge’s wait gives the source deposit time to become final before it signs a release.

For cBridge, the State Guardian Network (SGN) observes the source deposit, then signs the destination release after the source chain’s wait. The cBridge SGN adds the validator layer to this sequence: it connects the observed deposit to the authorization for funds to move on the destination chain.

Why do bridges wait for block finality?

Bridges wait because inclusion, confirmation and finalization are different stages. Inclusion means a transaction is in a block. Confirmations mean more blocks have been built after it. Finalization means the chain has reached a stronger point of assurance that the block will remain part of its history. Wallets can show confirmations well before finality.

A reorganization, or reorg, replaces part of a chain’s recent history. If a bridge releases destination funds while the source deposit is in a block that can still be replaced, the reorg can remove the deposit while leaving the payout intact. Waiting reduces that risk by delaying the release until the source chain’s required level of finality.

Finality works differently across chains, so a bridge’s wait depends on what the source chain can establish and what the bridge chooses to trust:

  • Ethereum: Casper FFG finalizes checkpoints. An epoch contains 32 slots of 12 seconds, and finalization usually takes about two epochs.
  • Bitcoin: Finality is probabilistic: each new block makes a reorg less likely, rather than making reversal impossible at a specific moment. Six confirmations is a common convention.
  • Rollups such as Arbitrum and Optimism: A sequencer can give a soft confirmation in seconds. The transaction reaches Ethereum finality once its batch is posted to Ethereum and that batch is finalized.

Think of a soft confirmation as a receipt from the sequencer: useful evidence that it accepted the transaction, but distinct from the later settlement record on Ethereum. A bridge that trusts the sequencer’s confirmation can move sooner. A bridge that waits for Ethereum to finalize the batch takes longer, often many minutes. The same rollup exit can therefore take seconds or much longer depending on which stage the bridge requires.

What sets the wait for a particular transfer?

The source chain and the bridge’s release rule set the wait. On a chain with probabilistic finality, a bridge may require a chosen number of confirmations. On Ethereum, it can wait for checkpoint finalization. On a rollup, the key question is whether the bridge accepts the sequencer’s soft confirmation or waits for the batch to become final on Ethereum.

That is why “confirmed” in a wallet does not necessarily mean “ready to release” at the bridge. The chain has included the deposit, but the bridge may still be waiting for more blocks or a finalized checkpoint. For cBridge, slower source-chain finality means a longer transfer before validators sign the destination release.

Related

What is a chain reorganization (reorg)?

A chain reorganization replaces recent blocks with a different version of the chain’s history. A deposit in a replaced block can disappear, which is why bridges wait before paying out against it.

Why do exchanges and bridges ask for different confirmation counts?

Exchanges and bridges set their own thresholds for when they treat a deposit as safe to act on. The number depends on the chain’s finality model and the service’s release rules, so a confirmed deposit can still be waiting for the bridge’s threshold.