[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog-content-en-what-is-blockchain-finality":3},{"slug":4,"title":5,"excerpt":6,"description":7,"bodyHtml":8,"faqItems":9},"what-is-blockchain-finality","What Is Blockchain Finality? When a Transaction Truly Cannot Be Reversed","\"Confirmed\" and \"final\" are not the same thing. Here is how probabilistic and deterministic finality differ, why Ethereum, Solana and TON settle on different clocks, and why bridges and exchanges make you wait.","Blockchain finality explained: probabilistic vs deterministic finality, reorgs, how finality works on Ethereum, Solana and TON as of 2026, and why cross-chain transfers and exchanges wait for it.","\u003Ch2>\"Confirmed\" isn't one thing\u003C\u002Fh2>\n\u003Cp>Your wallet says a transaction is confirmed. Can it still be undone? The honest answer is: it depends what \"confirmed\" meant. \u003Cstrong>Finality\u003C\u002Fstrong> is the guarantee that a transaction is permanently part of the chain — that no future reordering of blocks can erase it. Different blockchains reach that guarantee in different ways and on very different clocks, and the distinction between \u003Cem>included\u003C\u002Fem> (in a recent block) and \u003Cem>final\u003C\u002Fem> (irreversible) quietly drives how exchanges, bridges and merchants treat your money.\u003C\u002Fp>\n\n\u003Ch2>Probabilistic finality: certainty by depth\u003C\u002Fh2>\n\u003Cp>Proof-of-work chains — Bitcoin is the canonical case — never declare a transaction final at all. A competing branch of the chain could always, in principle, overtake the current one and rewrite recent history in a \u003Cem>reorg\u003C\u002Fem>. What protects you is economics: each added block makes rewriting exponentially more expensive, so the probability of reversal decays toward zero with depth. Hence the folk rule of waiting some number of confirmations — it is not a protocol guarantee but a risk threshold, chosen differently by every exchange and merchant.\u003C\u002Fp>\n\n\u003Ch2>Deterministic finality: certainty by vote\u003C\u002Fh2>\n\u003Cp>Most modern proof-of-stake networks add an explicit finality mechanism: validators representing a supermajority of stake vote on checkpoints, and once a checkpoint is finalized, reverting it is no longer a matter of out-mining anyone — it would require a coordinated attack that destroys a large fraction of all staked value. Ethereum works this way as of 2026: blocks are proposed continuously, but finality arrives when checkpoints are ratified, typically on the order of several minutes. The guarantee is categorical rather than statistical — which is exactly what custodians and bridges want to lean on.\u003C\u002Fp>\n\n\u003Ch2>Three chains, three clocks\u003C\u002Fh2>\n\u003Cp>The ecosystems WATS spans illustrate the spread. \u003Cem>Ethereum\u003C\u002Fem> separates fast inclusion (seconds) from full finality (minutes), and much of DeFi happily acts on inclusion while high-value settlement waits. \u003Cem>Solana\u003C\u002Fem> is built for speed: transactions are optimistically confirmed in well under a second, with a finalized status following shortly after as supermajority confirmation accumulates. \u003Cem>TON\u003C\u002Fem> reaches finality in seconds through its BFT-style validator consensus. None of these is \"wrong\" — they are different trade-offs between latency and the strength of the early guarantee, part of the broader comparison in \u003Ca href=\"\u002Fblog\u002Fevm-vs-solana-vs-ton\">EVM vs Solana vs TON\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Ch2>Why bridges and exchanges make you wait\u003C\u002Fh2>\n\u003Cp>Anything that acts \u003Cem>on another chain's behalf\u003C\u002Fem> must respect the source chain's finality. A cross-chain message sent before finality could be invalidated by a reorg — while the action it triggered on the destination chain lives on, unbacked. That is why serious cross-chain protocols wait for source-chain finality before delivering messages (see \u003Ca href=\"\u002Fblog\u002Fwhat-is-layerzero\">how LayerZero moves messages between chains\u003C\u002Fa>), and why exchanges credit deposits only after their confirmation thresholds. The waiting is not bureaucracy; it is the difference between relaying a fact and relaying a rumor — and it is why \u003Ca href=\"\u002Fblog\u002Fhow-to-bridge-crypto-across-chains\">bridging\u003C\u002Fa> takes minutes even when both chains are fast.\u003C\u002Fp>\n\n\u003Ch2>Reorgs in practice\u003C\u002Fh2>\n\u003Cp>Shallow reorgs — a block or two — are a routine, designed-for occurrence on probabilistic chains and typically harmless: displaced transactions return to the mempool and are re-included moments later. The dangerous case is a \u003Cem>deep\u003C\u002Fem> reorg that unwinds a payment someone already acted on; deterministic finality exists precisely to make that class of event a coordinated-attack scenario rather than bad luck. For an end user the practical takeaway is modest: for coffee-sized transfers, inclusion is plenty; for life-sized ones, wait for final.\u003C\u002Fp>\n\n\u003Ch2>How WATS fits in\u003C\u002Fh2>\n\u003Cp>A wallet that spans EVM, Solana and TON is juggling three finality models on your behalf, and \u003Ca href=\"\u002Fhot-wallet\">WATS\u003C\u002Fa> absorbs exactly that complexity: transaction status on each chain reflects that chain's own settlement rules, while you interact with one interface and one balance. The unification runs deepest in fees — every action is charged in one token, \u003Cstrong>ATS\u003C\u002Fstrong>, instead of the chain's native gas, via an \u003Cstrong>ERC-4337 paymaster\u003C\u002Fstrong> on EVM and an equivalent fee-payer\u002Frelayer on Solana and TON. ATS itself is a LayerZero OFT, so its cross-chain movement honors source-chain finality by design, and one ATS balance serves all three ecosystems. Collected ATS is burned from a 100M supply toward a 30M floor, the wallet stays non-custodial — you hold your keys, WATS never holds one — and WATS remains the first and only wallet to combine ERC-4337 and OFT single-token fees with that burn. The mechanics are on the \u003Ca href=\"\u002Fats-fee\">ATS fee page\u003C\u002Fa>.\u003C\u002Fp>",[10,13,16],{"q":11,"a":12},"What is the difference between a confirmed and a finalized transaction?","Confirmed usually means the transaction is included in a recent block — visible, but on some chains still theoretically reversible by a reorg. Finalized means the protocol guarantees it can no longer be undone: on proof-of-work chains that guarantee is statistical and grows with depth, while modern proof-of-stake chains reach an explicit, categorical finality once a validator supermajority ratifies a checkpoint.",{"q":14,"a":15},"How long does finality take on Ethereum, Solana and TON?","As of 2026, roughly: Ethereum includes transactions in seconds but reaches full checkpoint finality in several minutes; Solana confirms optimistically in under a second with finalized status following shortly after; TON finalizes in seconds via its BFT-style consensus. Exact figures evolve with protocol upgrades, which is why exchanges and bridges publish their own confirmation policies per chain.",{"q":17,"a":18},"Why does my cross-chain transfer take longer than a normal transaction?","Because the destination chain must not act on source-chain events that could still be reorganized away. Cross-chain protocols therefore wait for the source chain's finality before delivering the message and completing the transfer. The extra minutes are the cost of making sure the tokens minted or released on the destination are backed by a source-side event that can never be reversed.",1784634268788]