~$ crypto-under-the-hood

# The machinery behind the coins

~/notes / consensus and blocks

Finality Gadgets

The component that turns probabilistic confirmation into an explicit guarantee. What it promises and what it costs.

Ivan Kruse · · 2 min

Proof of work provides finality that strengthens with depth and never reaches certainty. A finality gadget provides an explicit point beyond which reversal requires destroying an enormous amount of stake.

How it works

Validators vote on checkpoints. When a supermajority votes for a checkpoint, it becomes justified. When a subsequent checkpoint is justified, the earlier one becomes finalised.

Reverting a finalised checkpoint would require a supermajority to have voted for conflicting checkpoints, which is a slashable offence. The cost of reversal is therefore a large fraction of the total stake being destroyed.

That is economic finality: not impossible, but catastrophically expensive.

What it gives users

A defined point of settlement. Rather than waiting an arbitrary number of confirmations for comfort, there is a specific moment after which the transaction is final under the protocol’s guarantees.

Predictable timing. Finality arrives on a schedule determined by the epoch structure, typically minutes rather than a variable number of blocks.

What it costs

Communication. Every validator must vote on every checkpoint, which requires aggregating a large number of signatures. This is what makes signature aggregation necessary rather than merely useful.

Liveness under partition. If too many validators are unreachable, finality stalls. The chain continues producing blocks and stops finalising them.

Designs include an inactivity mechanism that gradually penalises non-participating validators until the remaining active set can finalise again. It is slow by design, because the alternative is finalising with insufficient participation.

The failure mode worth knowing

A finality stall is not a halt. Blocks continue and are not finalised.

During one, transactions still process and the settlement guarantee is weaker. Venues typically respond by increasing confirmation requirements or suspending deposits, which is the correct response and is visible to users as a delay.

The comparison with probabilistic finality

Probabilistic. No explicit point. Confidence grows with depth. Simple, well understood, and the number of confirmations required is a judgement call.

Economic. Explicit point, faster, and the guarantee depends on the penalty mechanism working, which is more machinery and therefore more surface for bugs.

Neither is strictly better. They make different trade-offs between simplicity and speed.

The practical consequence

Confirmation requirements at venues reflect this directly. Networks with explicit finality are credited after finalisation; networks without are credited after a block count chosen to give equivalent assurance.

Those thresholds are published by platforms including a venue that supports immediate withdrawal, and comparing them across assets is a practical ranking of how much settlement assurance each chain provides, made by parties with money at stake in getting it right.

# Corrections and technical nitpicks are welcome. Send them over. They get published with the fix.

finalityconsensusguarantees

# related notes