b-money, Bit Gold and Hashcash: The Precursors to Bitcoin
Before Bitcoin there were Hashcash, b-money and bit gold. Here is what each proposal did, who made it, and which ideas Satoshi Nakamoto later combined.
Bitcoin did not appear from nothing. Its 2008 design combined several earlier ideas, most of them discussed on cryptography mailing lists through the 1990s and 2000s. Three of the best known are Hashcash, b-money and bit gold. Understanding what each did, and what each lacked, helps explain why Bitcoin looked new when it arrived.
Hashcash (1997)
Adam Back, a British cryptographer, proposed Hashcash in 1997. The goal was not money but spam control. A sender would have to find a number that, when hashed together with the email's details, produced a result with a certain pattern. Finding it required many attempts, while checking it took one. That asymmetry is the idea of proof of work.
The cost to a single sender was small, but the cost to a spammer sending millions of messages would be large. Hashcash was never widely used for email, but its proof-of-work mechanism is the same basic technique Bitcoin uses to secure blocks.
b-money (1998)
In 1998 Wei Dai, a computer engineer and cypherpunk, described b-money in a short essay posted to the cypherpunk mailing list. It sketched an anonymous, distributed electronic cash system in which participants kept their own records of who owned what and enforced contracts through collective rules.
Dai described two versions. In one, every participant maintained a database of all balances. In another, a smaller group of servers did the record-keeping and were required to put up deposits as a guarantee of honesty. The proposal also suggested creating money through proof of work. b-money was a concept rather than working software, and it left open important questions, such as how to keep the system secure against participants who cheated at scale.
Satoshi Nakamoto cited b-money in the Bitcoin whitepaper, and reportedly corresponded with Dai before release. Dai's essay is only a few pages long, yet it anticipated several features that later became familiar: pseudonymous participants identified by public keys, a record of balances kept by the community, and computational puzzles as the basis for creating money.
Bit gold (designed 1998, described publicly later)
Nick Szabo, a computer scientist and legal scholar, designed a mechanism he called bit gold around 1998, though his public description came several years later. The idea was to create digital scarcity by chaining together proof-of-work solutions. Each solution would be timestamped and added to a public record, and the result could be traded like a collectable asset with a cost built into its creation.
Bit gold had no complete implementation. It relied on a group of participants to keep a trustworthy record of who held what, and the details of that agreement were not fully specified.
What the three proposals had in common
| Proposal | Year | Main contribution | Gap |
|---|---|---|---|
| Hashcash | 1997 | Proof of work as a cost on actions | Not designed as money |
| b-money | 1998 | Distributed ledger of balances, money from work | No full security mechanism |
| Bit gold | 1998 design | Chained proofs of work as digital scarcity | No full consensus mechanism |
What Bitcoin added
The 2008 Bitcoin whitepaper tied these pieces together. It used proof of work not only to create new coins but to order transactions into a single, shared chain of blocks. The longest chain with the most accumulated work is treated as the valid one, and participants have an economic incentive to extend it honestly. That combination, a shared ledger that nobody controls and that is expensive to rewrite, addressed the double-spending problem without a central bank.
It is worth noting how much remained a design choice rather than inevitable. Earlier researchers had identified many of the same ingredients. The achievement was in assembling a complete system that could actually run and be joined by anyone.
Other digital money experiments
Hashcash, b-money and bit gold were proposals, but real systems existed too. The gold-backed e-gold service started in 1996 and attracted millions of accounts before US authorities took action against its operators in 2007; the company pleaded guilty in 2008 to charges including operating an unlicensed money transmitting business. Liberty Reserve, a digital currency service, was shut down by US prosecutors in 2013. Hal Finney's RPOW system from 2004 applied proof of work to create reusable tokens. All of these relied on a central operator, which made them easier to run and also easier to close.
That is the thread that Bitcoin changed. A single operator is also a single point of failure, a principle that applies to ordinary hosting setups too, where keeping backups away from your main server is standard practice (see our security page).
A note on attribution
Because Bitcoin's creator is pseudonymous, people have long speculated that one of the earlier authors might be Satoshi Nakamoto. Both Dai and Szabo have denied this, and no claim has been established. This article does not treat any of those theories as fact.
A practical lesson for site owners
The history shows how often a good idea needs several attempts before it works. For a business, that is an argument for making changes in stages, with backups and a way to roll back. Our knowledge base covers backups and the other everyday steps that keep a website recoverable when an experiment goes wrong.
