Finalized Block

Overview

Meaning and scope

A finalized block is a block that has satisfied the network’s formal finality rule and is not expected to be removed by normal fork choice or chain reorganization. Finalization may come from validator supermajority votes, a commit certificate, or another protocol-specific mechanism.

Mechanism and operation

In checkpoint-based systems, finalization can apply to a checkpoint and all valid ancestors; in instant-finality systems, a commit certificate can finalize each block directly. The evidence for finalization must be verified, not inferred from a block label returned by one RPC provider. A verifier checks the block root, ancestry, validator set, vote weight, signatures, and consensus period. Some APIs expose tags such as “finalized,” but the trust model depends on whether the client independently validates the Finality Proof or merely reports a remote node’s view. A transaction inside the block may have reverted, transferred a different asset, paid the wrong amount, or interacted with an unexpected contract.

Practical payment example

A settlement job anchors a transaction to a block flagged finalized under the network’s consensus rules. The job still verifies token transfer details; finality alone does not prove the correct beneficiary was paid.

Operational checks

Payment systems must combine block finality with execution status, event decoding, destination validation, and order matching. They should also verify that the block belongs to the intended network and canonical state. Operational records should preserve the block ID, block number, finalization time, proof reference, and the node or client that verified it.

Distinctions and limits

A finalized block has crossed the protocol-defined boundary after which compliant nodes will not replace it during ordinary consensus operation. It therefore differs from a Confirmed Block, which may simply have one or more descendants.

Related reading

Related definitions: Confirmed Block, Finality Proof.