The Predecessors

Bitcoin was not invented from nothing. For two decades, brilliant people built pieces of the puzzle. Studying them shows you precisely which gap Bitcoin filled — and proves the breakthrough was a synthesis, not a single trick.

The four key predecessors

Attempt	Year	Author	Contributed	Fatal gap
DigiCash / ecash	1989	David Chaum	Strong cryptographic privacy (blind signatures)	Centralized — a company issued the money
Hashcash	1997	Adam Back	Proof of Work	Built for email spam, not a currency/ledger
b-money	1998	Wei Dai	Everyone holds the ledger; work mints money	No concrete way to make everyone agree
bit gold	1998	Nick Szabo	Chained proofs of work; decentralized scarcity	No solution to ordering / double-spend

Let’s look at what each taught us.

DigiCash (David Chaum, 1989)

Chaum was decades ahead on privacy. His blind signatures let a bank certify a coin as valid without seeing who it belonged to — genuinely brilliant cryptography. But DigiCash was a company: a central issuer ran the ledger. When the company went bankrupt in the late 1990s, the money died with it.

Lesson: cryptographic privacy ≠ decentralization. Removing the middleman’s view is not the same as removing the middleman.

Hashcash (Adam Back, 1997)

Hashcash fought email spam by forcing the sender to perform a small, verifiable chunk of computational work for each email — cheap for one message, ruinously expensive for a spammer sending millions. The key idea: prove you spent real-world effort. This is the literal seed of Bitcoin’s Proof of Work, and Hashcash is cited in the Bitcoin whitepaper. But Hashcash was an anti-spam stamp, not money — it had no ledger and no notion of ownership.

Lesson: you can make digital actions costly and unforgeable by tying them to computation. (This is the “make influence expensive” idea from the last page.)

b-money (Wei Dai, 1998)

Wei Dai proposed a system where every participant keeps a copy of the ledger and computational work creates money. Conceptually this is strikingly close to Bitcoin. But it never specified a workable mechanism for the participants to agree on the ledger’s contents when they disagree — the Byzantine problem was left open.

Lesson: “everyone keeps a copy” is necessary but not sufficient. You still need a rule for resolving disagreements.

bit gold (Nick Szabo, 1998)

Szabo’s bit gold chained proofs of work together so that creating new units was provably costly and the chain recorded their order — decentralized digital scarcity. But it still lacked a robust, attack-resistant answer to who decides the one true ordering, leaving double-spending unsolved in practice.

Lesson: chaining work is part of the answer, but you need consensus on which chain counts.

The pattern: the missing keystone

Lay the lessons side by side and the gap is obvious. By 2008 the world already had, separately:

• Privacy (DigiCash)
• Proof of Work to make actions costly (Hashcash)
• A distributed-ledger vision (b-money)
• Chained, ordered scarcity (bit gold)

What nobody had was a way to combine them so that mutually-distrustful strangers in an open network converge on a single, hard-to-rewrite ordering of transactions — defeating both the Byzantine and Sybil problems at once.

That missing keystone is the subject of the final foundations page.

Check your understanding

1. What did DigiCash get right, and what was its fatal flaw?
2. What single idea did Hashcash contribute that Bitcoin reuses, and what is it used for?
3. How was b-money close to Bitcoin, and what did it leave unsolved?
4. By 2008, which four ingredients already existed separately — and what was still missing?