An essay
The problem Satoshi set out to solve
Bitcoin's creator left a nine-page paper, hundreds of forum posts and emails, and a newspaper headline in the very first block. Read together, they describe one problem with unusual clarity.
I A payment needs a referee
Every time you pay someone online, a third party sits in the middle: a bank, a card network, a payment company. It checks balances, settles disputes, and reverses payments when something goes wrong. Most of the time that works well enough.
But the Bitcoin whitepaper opens by pointing at the cost of the arrangement. Because payments can be reversed, it argues, merchants have to be wary of their customers, ask for more information than they would otherwise need, and accept a certain amount of fraud as unavoidable.1 Whitepaper, section 1, “Introduction.” Small, casual payments become impractical, and every transaction carries the overhead of mediation.
The paper's alternative fits in a sentence: a payment system based on cryptographic proof instead of trust, so that any two willing parties can transact directly.
II The copying problem
Digital information is easy to copy. That's wonderful for music and text and terrible for money: if a digital coin is just data, what stops someone from spending it twice? This is the double-spending problem, and it is the real puzzle the whitepaper solves.2 Whitepaper, section 2, “Transactions.”
Earlier digital cash systems had an answer: a central issuer that recorded every coin and refused duplicates. It worked, but it put a single company back in the middle — one that could freeze, censor, or simply shut down. When the company failed, its money failed with it.
Bitcoin's answer was to make the ledger public and let the whole network agree on one history. Transactions are announced to everyone; nodes bundle them into blocks; and each block carries a proof-of-work that makes rewriting history expensive. The chain with the most work behind it is the accepted record.3 Whitepaper, sections 4 and 5, “Proof-of-Work” and “Network.” No mint and no referee — just rules that anyone can check.
III A headline in the first block
Bitcoin's first block — the genesis block — is dated 3 January 2009. Inside it is a line of text:
The Times 03/Jan/2009 Chancellor on brink of second bailout for banks
It is, first of all, a timestamp: proof that the block couldn't have been created before that day's newspaper.4 The text is in the genesis block's coinbase transaction and matches the front-page headline of The Times of London on 3 January 2009. Many readers also see a comment on the financial crisis then underway. Satoshi never explained the choice in detail, so that reading is an interpretation — but it's a hard one to ignore.
A few weeks later, introducing the software on an online forum, Satoshi was more direct, describing the root problem with conventional currency as all the trust that's required to make it work.
5 Satoshi Nakamoto, post introducing Bitcoin on the P2P Foundation forum, 11 February 2009.
IV Standing on earlier ideas
Bitcoin didn't appear from nowhere. The whitepaper's short reference list cites Wei Dai's b-money proposal, Adam Back's Hashcash, research on secure timestamping by Stuart Haber and W. Scott Stornetta, and Ralph Merkle's work on public-key protocols.6 Whitepaper, “References.”
Hashcash used proof-of-work to make spam expensive. Timestamping research showed how to chain records so they couldn't be quietly backdated. b-money sketched money maintained by a network of pseudonymous participants.
What Satoshi added was the combination — and an incentive. New coins and fees reward whoever extends the chain by the rules, so the people who secure the network are paid by the network itself.7 Whitepaper, section 6, “Incentive.” That turned a set of research ideas into a system that strangers could run together.
V The author who left
By 2011, Satoshi had stopped communicating publicly, and their identity is still unknown. Whatever the reason, the effect is unusual: Bitcoin has no founder to arrest, pressure, or defer to. Changes to the rules have to persuade the people who run the software, because no one has the authority to impose them.
That absence fits the paper's argument. A system designed to work without trusted third parties ended up working without its own author, too.
VI Why ask why
Knowing the original problem helps when judging what's built around Bitcoin today. A useful test for any product or proposal is simple: does it bring back the trusted third party the paper set out to remove?
Sometimes that trade is worth it — custodial services can be convenient, for example — but it should be a choice made knowingly, not by accident.
- Who can reverse this payment?
- Who can freeze these funds?
- Whom do I have to trust — and what happens if they fail?