Transaction Finality

What Is Transaction Finality in Blockchain?

Transaction finality in blockchain is the moment a payment stops being provisional. A blockchain is a shared record kept by thousands of computers that do not trust one another. When some of them briefly disagree about the latest blocks, the network has to settle on one version, and any transaction that existed only in the losing version drops out. Replacing a recent stretch of history like this is called a reorganisation, or reorg.

Finality answers one question: from what point can that no longer happen to my transaction? Chains answer it in two quite different ways.

Probabilistic Finality: Counting Confirmations

Bitcoin never declares a transaction final. A transaction earns its first confirmation when a miner includes it in a block, and every later block adds another. Bitcoin.org's guidance notes that blocks arrive about every ten minutes on average, that transactions "do not become irreversible immediately", and that six confirmations is the minimum it recommends for high value transfers.

The reasoning goes back to the 2008 whitepaper: to rewrite a payment, an attacker has to outpace the honest chain, and the probability of a slower attacker catching up "diminishes exponentially as subsequent blocks are added." The risk never reaches zero. It simply becomes too small to matter, which is why this is called probabilistic finality.

Reorgs are not hypothetical. In March 2013 a software incompatibility split Bitcoin in two, and the official post-mortem, BIP 50, records that one side had to reorganise onto the other, that at least one large double spend happened during the split, and that major exchanges suspended deposits until it was over.

Deterministic and Economic Finality

Many proof of stake chains finalise blocks by explicit vote instead. On Ethereum, ethereum.org explains, time runs in 12 second slots grouped into 32 slot epochs, and the first block of each epoch is a checkpoint. When validators holding at least two thirds of staked ETH vote for a pair of checkpoints, the earlier one becomes finalized, normally after two epochs, or about 13 minutes by that arithmetic. Reverting a finalized block would cost an attacker at least a third of all staked ETH, destroyed through slashing. That is economic finality: reversal is possible in principle, but its price is written into the rules.

Some chains finalise every block. The Cosmos documentation describes its CometBFT engine as giving instant finality: "once a block is committed, it cannot be reverted." Solana's documentation separates a "confirmed" block, voted on by more than two thirds of stake, from a "finalized" one, and warns that its earliest "processed" status "can still be rolled back."

The trade off is that voting can stall. If more than a third of stake stops voting, nothing can be finalised, and on Ethereum an inactivity leak starts after four epochs without finality, bleeding stake from validators who are not voting with the majority until a two thirds majority returns.

Why Exchanges Wait for Confirmations

An exchange that credits a deposit which a reorg later erases has paid out for coins it never received: the classic double spend. Kraken says it holds deposits for a set number of confirmations "to avoid the risks of double spending", because more confirmations make a transaction more permanent. Cross-chain bridges face the same problem in a sharper form, since they release funds on one chain against events on another.

The practical rule: "confirmed" in a wallet often means included in a block, not final. For a large payment, find out what finality means on that particular chain and wait for it. Speed claims matter less than the answer to a different question: what would it cost someone to undo this?