Finality Detection
Pronunciation: fy-NAL-ih-tee dih-TEK-shun
Also known as: Finality Recognition, Finality Status Detection
Definition
Finality detection is the process by which software determines that a block or transaction has reached the finality condition defined by its blockchain protocol or business policy. The system may inspect finalized checkpoints, validator certificates, masterchain inclusion, or confirmation thresholds. Detection must distinguish protocol finality from application acceptance and must handle stale nodes, delayed APIs, reorganizations, and provider disagreement.
Overview
Meaning and scope
Finality detection is the process by which software determines that a block or transaction has reached the finality condition defined by its blockchain protocol or business policy. The system may inspect finalized checkpoints, validator certificates, masterchain inclusion, or confirmation thresholds. Detection must distinguish protocol finality from application acceptance and must handle stale nodes, delayed APIs, reorganizations, and provider disagreement.
Mechanism and operation
Finality Detection converts protocol evidence into an operational decision. On a deterministic-finality network, software may verify a commit certificate or finalized checkpoint. A node can expose a finalized block tag, a consensus client can report finalized checkpoints, or a TON payment processor can verify that a shardchain transaction was included in a finalized masterchain block. Detection should preserve the chain, block hash, height, evidence type, and observation time. If two providers disagree, the application should not silently select the most favorable answer. It should evaluate synchronization, source trust, and whether the providers are describing different stages of the same transaction.
Practical payment example
A payment monitor sees six blocks after a transfer but the selected chain exposes a separate finalized checkpoint. It records the checkpoint proof as its finality signal instead of equating arbitrary depth with finality.
Operational checks
A finalized transfer can still be the wrong asset, amount, or destination, while a merchant can choose to accept a payment before protocol finality under a defined risk limit. The finality detector supplies evidence to the business state machine rather than replacing it. Monitoring should continue for unusual conditions such as Finality Delay, API lag, invalidated traces, or consensus incidents.
Distinctions and limits
On a proof-of-work network, it may measure confirmations and apply a risk threshold based on Probabilistic Finality. Reading only the latest observed block is not enough.
Related reading
Related definitions: Finality, Probabilistic Finality.
Example
A payment monitor sees six blocks after a transfer but the selected chain exposes a separate finalized checkpoint. It records the checkpoint proof as its finality signal instead of equating arbitrary depth with finality.
Comparison
On a proof-of-work network, it may measure confirmations and apply a risk threshold based on Probabilistic Finality. If two providers disagree, the application should not silently select the most favorable answer. It should evaluate synchronization, source trust, and whether the providers are describing different stages of the same transaction.
Key Takeaway
Finality detection verifies protocol-specific settlement evidence and feeds it into payment policy without confusing network finality with business acceptance.
Sources
- Ethereum.org Proof-of-Stake Frequently Asked Questions — Ethereum.org (2026-08-02)
- Ethereum.org Documentation: Gasper — Ethereum.org (2026-08-02)
- TON Documentation: Payment Processing Overview — TON Documentation (2026-08-02)
- TON Documentation: How to Adopt Sub-Second Finality — TON Documentation (2026-08-02)