Cypherpunk
1980s–
The cypherpunks believed that cryptography was a tool for autonomy — that mathematical privacy protection, in the hands of ordinary people, could resist surveillance, censorship, and centralized control in ways that laws and politics could not.
The Core Argument
Eric Hughes’ A Cypherpunk’s Manifesto (1993) opens: “Privacy is necessary for an open society in the electronic age.” Not secrecy — privacy. The distinction matters. Secrecy is hiding things from everyone. Privacy is selectively revealing yourself, on your terms, to people you choose.
The manifesto continues: “We cannot expect governments, corporations, or other large, faceless organizations to grant us privacy out of their beneficence… We must defend our own privacy if we expect to have any… Cypherpunks write code.”
That last line is the tradition’s method. Don’t lobby for privacy. Build tools that make surveillance structurally difficult. Make privacy something you have by default, not something you have to ask for.
What It Built
The tradition runs from the early-1990s Cypherpunks mailing list through to the present:
- PGP (Phil Zimmermann, 1991) — encrypted email, which nearly got Zimmermann prosecuted under arms export law
- SSL/TLS — built at Netscape, not by the cypherpunks; but in 1995 list members publicly cracked its export-weakened 40-bit mode, a demonstration against crypto export limits
- Tor — anonymous routing, originally funded by the US Navy, now used by journalists, dissidents, and anyone who needs to communicate without surveillance
- Bitcoin (Satoshi Nakamoto, 2008) — stateless digital currency; the whitepaper cites Wei Dai’s b-money directly
- Ethereum — programmable cryptographic agreements; Buterin’s extension of the project
The Tension With Openness
The free software movement and the cypherpunk tradition share values but pull in different directions. Free software wants code to be transparent and modifiable by everyone. Cryptography wants some communications to be unreadable by everyone except the intended parties. Both are tools for autonomy; they just protect different surfaces.
The synthesis is something like: open tools, private data. The infrastructure should be auditable and modifiable (free software principle). The communications and transactions running on that infrastructure should be private by design (cypherpunk principle). Neither transparency nor opacity as defaults — appropriate disclosure.
The Darker Thread
Cypherpunk libertarianism has a shadow side: the belief that technical solutions can replace governance, that code can stand in for law (Lawrence Lessig’s phrase “code is law” was a warning, not a creed), that mathematical systems are neutral and institutions are not. This produces both genuine innovation (cryptocurrencies, zero-knowledge proofs) and genuine pathology (markets with no recourse, systems that can’t be corrected when they fail, communities that fetishize mechanism over meaning).
Buterin’s d/acc is partly a response to this — an attempt to take the tools seriously while being honest about what they require socially to work.
Key Figures
- Eric Hughes — the manifesto
- Tim May — the crypto-anarchist papers
- Phil Zimmermann — PGP, fought for the right to encrypt
- Wei Dai, Nick Szabo — b-money, bit gold; direct ancestors of Bitcoin
- Vitalik Buterin — programmable cryptographic agreements
Key Documents
- A Cypherpunk’s Manifesto (Hughes, 1993)
- The Crypto Anarchist Manifesto (May, 1988)
- Bitcoin whitepaper (Nakamoto, 2008)
Connections
- free-software-movement — parallel tradition, shared values
- Vitalik Buterin — the contemporary extension
- appropriate-technology — cryptographic tools as appropriate technology
- commons — the governance question cypherpunk often skips
“Cypherpunks write code.” The manifesto was right about the method. The question it left open was what the code should be for.