Finality models
- Probabilistic (Bitcoin, most PoW) — a block is more final the deeper it’s buried. After 6 confirmations (~1 hour on Bitcoin), reorg probability is vanishingly small. Never strictly zero.
- Economic finality (Ethereum PoS) — after two epochs (~12.8 minutes), a block is “justified” and “finalized” by 2/3+ validator attestations. Reverting requires 1/3+ of validators to be slashable, costing billions of dollars in stake.
- Deterministic / BFT finality (Tendermint, HotStuff) — once a block is signed by 2/3+ validators within a round, it’s immediately final. Cosmos chains, Algorand, Aptos, Sui work this way.
- Rollup finality — L2 transactions are confirmed on L2 quickly (seconds) but only final on L1 after the L1 settlement lands. For optimistic rollups, that’s ~7 days (the challenge window); for ZK rollups, minutes to hours once the proof verifies.
Why finality matters
For high-value use cases (institutional settlement, exchange deposits/withdrawals), the question “when is this transaction safe to treat as irreversible?” has a specific answer per chain:
- Bitcoin — major exchanges require 3-6 confirmations (30-60 minutes).
- Ethereum PoS — 2 epochs (~12.8 minutes) for economic finality. Most exchanges credit after 32-64 blocks.
- Solana — ~400ms optimistic confirmation, ~12s max slot finalization. Most exchanges credit after 32 slots (~13s).
- Cosmos BFT chains — immediate finality (1-2 block times).
Finality anomalies
Not all claimed “final” transactions stay that way:
- Ethereum reorgs — occasional 1-2 block reorgs happen due to late blocks or MEV-driven reordering. Rare past 2-3 confirmations.
- Solana outages — during network stalls (halted processing during congestion), “final” blocks have been rolled back after validator restart.
- L2 chain rewinds — some L2s have rolled back state via emergency multisig action after discovering exploits. Users treating L2 confirmations as truly final have been surprised.
Risks and considerations
For developers: understand your chain’s finality model before designing applications. A DEX that assumes instant finality will fail in subtle ways on a chain with probabilistic finality. Cross-chain bridges must typically wait for destination-chain finality before acting on source-chain events.
For users and traders: the practical rule is “wait for enough confirmations that your counterparty is satisfied.” Exchanges publish their confirmation thresholds explicitly. For very large transfers, waiting 15-30 minutes past the published threshold is cheap insurance against the rare deep reorg.
For institutions: finality guarantees interact with regulatory expectations around settlement. The BIS and FSB have published frameworks for “settlement finality” in crypto that align most closely with economic-finality PoS chains and BFT-style instant finality — which has pushed infrastructure adoption toward those designs.