A protocol-defined state in which reversing a block requires violating that network's consensus assumptions and incurring its specified cost. It differs from a wallet confirmation, sequencer response, or settlement on another chain.
Supports: ethereum.org explains Ethereum checkpoint finality, two-thirds voting, and the crypto-economic cost of reverting finalized blocks.
Supports: ethereum.org distinguishes crypto-economic finality from probabilistic finality and explains the required staked-ether vote.
Finality is protocol-specific and distinct from a UI confirmation, L2 inclusion, or settlement elsewhere
Ethereum proof-of-stake checkpoint finality is crypto-economic and relies on supermajority voting
Timing, reorganization exposure, and withdrawal conditions vary across networks and upgrades
Check the relevant chain and transaction path instead of relying on universal confirmation counts
Before treating a transfer as settled, a user checks the receiving service's requirements, the source chain's current finality state, and any bridge or L2 withdrawal path. They do not use a sequencer acknowledgement or another chain's advertised timing as proof of final settlement.
A node in a Rollup (L2) responsible for ordering transactions before they are batched and sent to the L1 (Ethereum).
A block-production design that separates building an execution payload from proposing a consensus block. Implementations can use external relays or protocol rules, with different trust and censorship properties.
A blockchain's own consensus and settlement layer. The label describes where that protocol processes and orders transactions; security, finality, data availability, and scaling guarantees differ by chain and design.
The protocols, incentives, and rules that let distributed network participants select and validate a shared ledger state despite delays, faults, or conflicting proposals.
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles