Sign in

The Bitcoin design philosophy

Suggest an edit

Bitcoin is the first chain you'll meet in detail, and the one every later chain measures itself against, because it came first and proved the model worked. Its design choices look strange in isolation: ten-minute blocks, a scripting language that can't loop, a money supply hardcoded to stop at twenty-one million. Each one falls out of a chain of reasoning that starts with a single question.

Electronic cash with no operator

In late 2008, a paper appeared on a cryptography mailing list. The author used the pseudonym Satoshi Nakamoto, and the paper was titled "Bitcoin: A Peer-to-Peer Electronic Cash System."

Each word of the title is a requirement. Electronic ruled out paper currency and required a system that could exist purely as data, transmitted over the internet. Cash ruled out anything that required a third party to clear the transaction, which is what makes physical cash different from a bank transfer. Two people standing in a room exchanging cash do not need permission from a bank to complete the exchange. Peer-to-Peer ruled out a central server that the transaction flows through. System meant the whole apparatus had to work, end to end, at internet scale, with strangers, indefinitely.

Together the words ask for a way for any two parties anywhere in the world to exchange digital value directly, without permission from any third party, in a system that runs itself.

This had been an open problem in computer science for over twenty years before 2008. Several serious attempts had been made, and none of them had solved one problem without a central server keeping the books: how do you prevent the same digital coin from being spent twice in two different places? This is called the double-spend problem.

Bitcoin's contribution was an answer to this question that nobody had thought of before. The rest of the design follows from how that answer worked.

No operator means five constraints

Once you commit to no central operator, the system has to survive adversarial conditions. With no operator to ban attackers, it has to keep running while bad actors try to break it from the inside. Every design choice that follows is made under the assumption that an unknown fraction of participants are hostile.

That requirement produces five constraints.

Sybil resistance without identity. In any open system, the obvious attack is to create a million fake participants and outvote the honest ones. If the system uses identity to prevent this, it needs a way to identify people, which requires a central authority. So the system can't use identity. It needs some other way to make participation costly enough that creating a million fake participants is not economically feasible.

Public verifiability. Without a trusted operator to vouch for transactions, every participant has to be able to verify every transaction themselves. This means the rules must be simple enough to compute, the data must be available to everyone, and the verification must produce the same answer on every honest node.

Convergence despite network delay. Information traveling across the internet doesn't arrive everywhere at the same instant. Two participants on opposite sides of the world might see different events first. The system has to handle this, with all honest participants eventually agreeing on the same history, despite never having a synchronized clock or instant global broadcast.

Censorship resistance. If any single party can prevent a transaction from being processed, that party is effectively the operator. The system has to be structured so that no single point of failure can stop anyone from transacting.

Permanence. A transaction that settled yesterday has to be just as settled tomorrow. There's no operator to reverse it, and if the system could selectively forget or rewrite history, no payment would ever be final.

Each constraint picks one design choice

Each constraint rules out a category of possible designs, and each of the five choices below is Bitcoin's response to one of them.

Bitcoin's five constraints mapped to their design choicesA table lists five constraints on trustless peer-to-peer cash next to the Bitcoin design choice that answers each one, with arrows connecting each pair. Permanence leads to an append-only hash-linked log, Sybil resistance without identity leads to proof of work, public verifiability leads to simple deterministic validation, convergence under network delay leads to slow block times, and censorship resistance leads to an open permissionless network. Trustless peer-to-peer cash no operator, no permission Constraint Design choice Permanence settled means settled forever Append-only hash-linked log rewriting one block breaks all later ones Sybil resistance without identity no membership list Proof of work votes priced in real electricity Public verifiability anyone checks the rules Simple deterministic validation limited script, no loops Convergence under network delay no synchronized global clock Slow block times ten minutes, conservative on purpose Censorship resistance no single point of control Open permissionless network anyone runs a node, mines, transacts From one goal, five constraints. From the constraints, five design choices.

The ledger is append-only and hash-linked. A system with mutable history violates permanence. In Bitcoin each block carries the hash of the previous one, the structure you've already seen in the What is blockchain lesson, so rewriting a single old block invalidates every block after it.

Sybil resistance comes from proof of work. A system with a membership list would need someone to keep the list. So the right to add to the ledger is sold to whoever can demonstrate the most computational work. Computation costs electricity, and electricity costs the same regardless of how many identities you control, so a million fake participants pay a million times the bill.

Validation is deterministic and simple. A system with encrypted state violates public verifiability, because outsiders could not check it. In Bitcoin every transaction can be checked by running a small piece of code against the chain's state. The code is written in a deliberately limited language called Script, which has no loops or recursion and no access to external state, so every node running honest software reaches the same answer on the same input.

Block times are slow on purpose. A system that relies on a global synchronous clock cannot work, because the network has none. Bitcoin leaves room for network delay instead. A new block has to propagate to most of the planet before the next one is produced, so that everyone is building on the same most recent block, the tip of the chain. A block needs seconds to cross the network, and ten minutes is 600 seconds, so the delay is a small part of the interval. With a block every ten seconds, the delay would take up much of the interval, and there would be more chain forks and more wasted work. Ten minutes between blocks is a margin of safety for the network.

The network is open to anyone. A system where a gatekeeper can drop transactions violates censorship resistance. In Bitcoin anyone can run a node, mine, and transact without asking permission, so there is no single point of control.

Two more choices are not answers to any of the five constraints.

The money supply is capped. There will never be more than twenty-one million bitcoins. Block rewards halve every 210,000 blocks, which is about every four years, so the rate of new issuance slows over time and eventually stops. This is a deliberate economic choice and not a technical requirement. It is intended to make Bitcoin a credible store of value in a world where every other currency can be inflated by whoever issues it, and it is built into the protocol so that no one can change it.

The system changes slowly. This follows from having no operator. No central party can update the rules, so any change has to be accepted by the people who run nodes, and they have strong reasons to be conservative. The system is intentionally hard to upgrade, and developers strongly prefer changes that are backwards-compatible.

What Bitcoin gave up

The design has costs. Settlement takes minutes for a payment and hours for high-value transactions. Bitcoin is expensive at scale, because every node has to validate every transaction and there's a hard limit on how many can fit in a block. Script can't be used to build the complex applications that later chains support. Changes that other chains release in months take Bitcoin years. The last lesson of this module, What Bitcoin gave up and what it gained, weighs these costs against what they buy.

From here, the question is how the specific Bitcoin design works, top to bottom.