Finality is the point at which a transfer cannot be undone. Different blockchain designs reach that point in fundamentally different ways, and some never reach it absolutely.
Why finality is a question at all
In traditional settlement, finality is defined legally. A rulebook or statute states the moment a transfer becomes irrevocable, and courts enforce that definition.
Blockchains have no such authority. Finality emerges from the protocol's rules about which chain participants accept as valid, which is a technical rather than legal condition.
That shifts the question from what the law says to what the network would do if presented with a competing history of transactions.
Probabilistic finality in proof of work
In a proof of work system, a transaction is included in a block, and later blocks build on it. Reversing it requires rebuilding that chain with more accumulated work.
Each additional block makes reversal more expensive, so confidence rises with depth. It never reaches certainty, only a probability high enough to be treated as settled.
Exchanges and merchants set confirmation thresholds accordingly, and the number varies by asset and by the value at stake rather than by any protocol rule.
Deterministic finality in consensus designs
Some proof of stake systems finalize blocks explicitly. Validators vote, and once a supermajority commits to a block, reverting it requires violating protocol rules with penalties attached.
The penalty mechanism, often called slashing, makes reversal economically self-destructive for the validators who would have to carry it out.
Finality in these systems arrives at defined intervals rather than gradually, so a transaction is either finalized or not rather than more or less confirmed.
What a reorganization does
A chain reorganization occurs when nodes switch to a different chain, orphaning blocks they previously accepted. Transactions in orphaned blocks return to a pending state.
Short reorganizations happen routinely as a normal result of propagation delay. Deep ones are rare and usually signal either an attack or a serious client-level failure.
Any system built on a chain must handle this, which is why exchanges credit deposits only after their confirmation threshold rather than on first sight.
Why layered systems complicate the picture
Transactions on rollups and other layered systems settle first on the layer itself and only later on the underlying chain, creating two distinct finality moments.
Some designs include a challenge window during which a state claim can be disputed, meaning withdrawals to the base layer wait until that window closes.
A user experiencing an instant transaction on the layer and a delayed withdrawal is seeing the same distinction that separates local confirmation from settlement.