The story
In March 1997 the British cryptographer Adam Back announced Hashcash, a scheme to fight junk email and denial-of-service attacks by making senders pay with computing effort. To send a message, a sender's software must find a stamp, a short string containing the recipient's address and the date, whose cryptographic hash begins with a required number of zero bits. Since hash outputs cannot be predicted, the only way to find such a stamp is trial and error, which takes a moment of computer time. The recipient can check it with a single hash.
The idea of making senders do work had been proposed in 1992 by Cynthia Dwork and Moni Naor, and Hashcash grew out of the cypherpunks, a mailing list of cryptography activists who wanted privacy tools and untraceable digital cash. A stamp typically needed about 20 bits of work, a fraction of a second for a legitimate sender but costly for mass mailers. Hashcash was never widely adopted for email, partly because spammers could use hijacked computers. Its lasting influence was the principle that work can serve as proof: anyone can cheaply confirm that effort was spent. Bitcoin's 2008 whitepaper cites Hashcash as the basis of mining, where participants race to find hashes below a target and the winner adds the next block.
Why it mattered
- Bitcoin mining uses the same asymmetry, hard to produce and easy to check, to secure the blockchain without a central authority.
- b-money and Bit Gold built digital-money designs on proof of work, and Hal Finney's reusable proofs of work extended it.
- Proof of work became a way to make attacks costly, which shaped ideas about spam, denial of service and Sybil attacks.
- Hashcash established a concrete link between computing effort and economic cost, which was needed for digital scarcity.
Sources
- Genesis Files: Hashcash, or how Adam Back designed Bitcoin's motor block Bitcoin Magazine
- Satoshi Files: Adam Back CoinMarketCap Academy
Drafted by AI (Claude) from the sources above and checked against them by AI; no historian has reviewed this page. Spot a mistake? Suggest a correction. How pages are made
Community notes
Loading notes…