Blockchain Transaction Finality

Blockchain transaction finality is the assurance that a transaction recorded on a blockchain is permanent: it cannot be reversed, changed or dropped from the ledger. Exchanges, payment processors, custodians and ordinary users rely on it to decide when it is safe to treat incoming funds as received, to release goods or to credit an account.

Finality on a blockchain is a technical property produced by the network's consensus mechanism. It is related to, but not the same as, settlement finality in traditional payment and securities systems, which is a legal status conferred by statute and system rules. A blockchain transaction may be practically irreversible without any law recognising it as final, and regulators treat the gap between the two as a central question for digital asset markets.

In networks that use proof of work, such as Bitcoin, finality is never absolute. Each new block built on top of the one containing a transaction makes it harder to undo, because an attacker would need to redo the work for all of those blocks and overtake the honest chain. The probability of reversal falls rapidly with each block confirmation but does not reach zero. This model is described under probabilistic finality.

In practice, recipients choose a number of confirmations that matches the value at stake. Six confirmations, about an hour, is a long-standing convention for Bitcoin; exchanges set their own thresholds per asset and raise them for chains with less mining power. A transaction that has been broadcast but not yet included in a block has no finality at all.

Other networks provide explicit finality: once a defined step is completed, the protocol itself will not revert the block. Systems based on Byzantine fault tolerance (BFT), including those built with Tendermint, finalise each block as soon as validators holding more than two thirds of the voting power have signed it. Finality arrives within seconds, at the cost that the chain halts if too many validators are offline.

Ethereum, since its move to proof of stake in 2022, combines both approaches. Blocks are proposed every twelve seconds and are provisional at first. Validators vote in checkpoints, and when two successive checkpoints gather votes from two thirds of the staked ether, the earlier blocks become finalised, normally after about thirteen minutes. Reverting a finalised block would require at least one third of all stake to be destroyed through validator slashing, which gives what is called economic finality.

Before finality, a transaction can disappear through a chain reorganisation, in which nodes switch to a competing branch that does not include it. Short reorganisations occur naturally when two blocks are produced at nearly the same time, and the network's fork choice rule decides which survives. Deliberate reorganisations are the basis of the 51% attack, in which a party controlling most of the mining power or stake rewrites recent history to carry out double spending. Several smaller proof-of-work chains have suffered such attacks.

Finality at the protocol level does not protect against everything. A community can agree to change the rules and reverse an outcome, as happened on Ethereum in 2016 after the DAO hack. Tokens issued by a central party may be frozen or reissued under the issuer's own powers. And a transaction can be final yet mistaken: funds sent to the wrong address are gone.

Networks that process transactions off the main chain and post results to it add further stages. On a layer 2 network, a transaction is first confirmed by the operator within seconds, which is a promise and not finality. It gains stronger assurance when its data is posted to the base chain and that base block is finalised. On an optimistic rollup, withdrawals to the base chain must additionally wait out a challenge window, commonly about seven days, during which an invalid result can be disputed. A zero-knowledge rollup reaches finality once a validity proof is verified on the base chain. Assets moved through bridges inherit the weakest finality of the chains and intermediaries involved.

For payments, the time to finality determines how soon a merchant or exchange can act without risk. For institutional settlement it is more demanding. Standards for financial market infrastructures require final settlement to be clear and certain, by the end of the value date at the latest. Probabilistic settlement fits poorly with that requirement, since it leaves open a small chance that a completed delivery is unwound, and with it the linked payment.

Regulated platforms have responded in several ways: using permissioned ledgers with deterministic finality, defining in their rulebook the moment at which a transfer is legally final regardless of the technical state, and seeking designation under settlement finality law where available. Banking regulators have also cited uncertain finality as one reason for cautious treatment of assets on permissionless blockchains. For individual users, the practical rule is simpler: wait for the number of confirmations, or the finalised status, that the receiving party requires. The concept parallels payment finality in conventional systems.