Finality

Overview

Finality describes when ledger history becomes stable enough for applications to treat it as settled. Some networks produce explicit finalized checkpoints through validator quorum, while proof-of-work networks generally gain probabilistic confidence as additional work builds above a block. Finality is different from transaction execution and recent inclusion. A transaction can succeed in a block that is later reorganized, and a network can keep producing blocks while its stronger finality process stalls.

Payment systems should use network-specific finalized or confirmation criteria based on value and risk. They should record the canonical block hash and detect reorganizations or delayed finality. Cross-chain protocols often need stricter source finality because reversing a source event after destination minting can create unbacked value. Verification of Finality needs the canonical block or checkpoint, active validator or consensus set, correct weights and thresholds, and the software version that interprets the evidence. When evaluating Finality, a provider’s status label is not enough when the native proof or checkpoint can be checked.

Payment policy based on Finality should distinguish detected, included, executed, confirmed, and finalized states. When evaluating Finality, high-value or irreversible fulfillment may require stronger evidence than routine acceptance, and exceptional network incidents need a review path rather than an automatic downgrade.

Production monitoring should track chain progress, delayed or conflicting checkpoints, participation, reorganization, and changes introduced by network upgrades. Records should preserve the block and evidence used when a business decision became irreversible. Finality should be defined by the exact protocol condition that makes a block, checkpoint, or state difficult or impossible to revert. When evaluating Finality, confirmation depth, local node acceptance, economic cost, and protocol finalization are related but distinct forms of assurance.