💡 The Plain-English Definition
The CAP theorem is a computer-science principle that says any distributed system — one spread across many independent computers — can guarantee only two of three properties: Consistency, Availability, and Partition tolerance. Bitcoin made a deliberate choice among them, and that choice is why Bitcoin transactions aren’t instantly final.
🤔 But Why Though?
Eric Brewer proved the CAP theorem in 2000. It says that when a network is split — when some computers temporarily can’t reach the others — a distributed system has to choose. It can stay consistent (every computer agrees on the same data, even if that means refusing to respond during the split), or it can stay available (every computer keeps responding, even if some give slightly out-of-date data). It can’t guarantee both at once.
Bitcoin chose Availability and Partition tolerance over strict Consistency. Its nodes — the computers each keeping a full copy of the ledger — keep running and accepting transactions even when they temporarily can’t reach each other. If the network splits for a moment, different parts may briefly disagree on which block is the latest, producing orphan blocks: valid blocks that compete for a short time before one chain wins. The network sorts this out within minutes, but during those minutes strict consistency is given up.
This is why Bitcoin has probabilistic finality — certainty that builds by odds — rather than instant finality. One confirmation means the transaction is very likely to stick. Six means it’s essentially certain for any practical purpose. A hundred blocks deep, it’s effectively permanent.
🌍 The Real-World Analogy
Think of two post-office branches sharing one customer database. If the connection between them drops, they face a choice: stop handling mail entirely until the connection comes back (consistent but unavailable), or keep handling mail from their last known records (available but possibly out of sync). Bitcoin is the branch that keeps handling mail — accepting that two branches might briefly disagree, and sorting it out once the connection returns. A little brief uncertainty is worth the benefit of never going down.
⚡ So What?
Understanding Bitcoin’s CAP choice explains why confirmations exist, and why six is the traditional bar for large transactions. It also explains why Bitcoin can never have truly instant finality at the base layer — the main chain itself, as opposed to systems built on top of it. Instant finality there would mean giving up either decentralisation or availability, and both are central to what Bitcoin is. So when someone complains that Bitcoin transactions aren’t “instant,” they’re really asking for a different CAP tradeoff — one that gives something else up instead.
