Eric Hughes is a cypherpunk and the author of A Cypherpunk’s Manifesto. Cypherpunks sought to protect privacy through cryptography: mathematical techniques for protecting and verifying information. Hughes stressed both personal choice and practical work. Demanding privacy is not enough; systems that support it must be built and used.
When you want to write privately, wishing that nobody else will read the message is not enough. The tool you send it through matters too. Eric Hughes urged this move from intention to action in A Cypherpunk’s Manifesto, signed and dated 9 March 1993. He called on people to build privacy protections themselves through software, encryption and other tools. The manifesto primarily explains a motivation and a direction of work. It is not a technical manual for judging every later application merely because it identifies with the cypherpunks. [1]
In the 1993 text, Hughes distinguishes privacy from complete secrecy. The aim is not for nobody ever to know anything about you, but to preserve the choice of what to disclose and to whom. He calls this selective disclosure. Imagine sharing personal news with a friend without wanting it posted on a public noticeboard. Sharing with that friend is compatible with privacy; the intended audience matters. Encryption can help protect the contents during communication. Once the recipient knows them, however, mathematics alone cannot prevent them from discussing the information further. [1]
Hughes uses an ordinary example in the 1993 manifesto: buying a magazine in a shop and paying cash. The seller needs to know what you are buying and that you have paid, not necessarily your name. Data minimisation does not mean the other party knows nothing about the transaction. The seller knows the goods and amount, and may have seen you. The point is to limit information to what the exchange needs. The same question helps when using a digital service: does this particular function really need every detail it requests? This is not a claim that every situation has identical requirements, but a way to distinguish necessary information from unnecessary disclosure. [1]
The 1993 manifesto connects privacy with writing and sharing software. Source code is the readable set of instructions from which a program is made. Publishing it lets others study the approach, try changes and look for defects. Imagine the difference between a finished device with no explanation and one with accessible plans. Plans make inspection easier, but their availability does not prove that a security audit occurred or that nothing was overlooked. Hughes’s call provides an important starting point for practical work. Evidence for a particular result still depends on what was actually checked. [1]
At the end of the 1993 manifesto, Hughes connects widespread privacy with social cooperation. This is not just a mathematical task for a programmer. To exchange messages securely, the recipient needs an appropriate tool too, and both people need to understand how to use it. If the recipient publishes what you entrusted to them, protecting transmission alone cannot solve that. Availability, usability and agreement between people therefore matter. A working mechanism is part of the answer; deployment and actual use show whom it helps and in what circumstances. [1]
Before the manifesto, Hughes was already working on a message-forwarding service. In a post dated 25 September 1992, he published a hopping remailer, a prototype able to forward a message through successive steps. A remailer is a forwarding service; this software rewrote email headers, the information used for delivery, and passed along another forwarding instruction. Hughes described a test in which he repeatedly sent a message to himself and observed its successive passes. The archive therefore reveals specific code and what the author actually tried. This was a documented routing test, not an operational anonymity audit. [2]
At the end of the 1992 post, Hughes warns that this system is not secure by itself. He describes adding encryption as the next project: the contents would be encrypted beforehand, with the relevant layer decrypted before the header was rewritten. The aim was to hide routing instructions from prying eyes. That feature was not part of the solution just demonstrated. It is a useful lesson when reading any development history: a prototype can accomplish a limited task while still lacking the protections expected of a finished product. A future plan must not be mistaken for an already verified capability. [2]
Hughes helps explain why people started building open tools for private communication and digital money. The 2008 Bitcoin whitepaper, however, describes its own payment mechanism under the name Satoshi Nakamoto: verifying payments and resisting repeated spending of the same funds without a central administrator. Hughes’s manifesto and message-forwarding work do not by themselves establish authorship of that protocol. His documented contribution is different and significant in its own right: he clearly explained the value of personal choice and connected the defence of privacy with actually writing and sharing code. [3]
For the clearest picture, read this entry together with Timothy May, Len Sassaman, A Cypherpunk’s Manifesto, Bitcoin Privacy. The reverse links also lead from The Crypto Anarchist Manifesto, A Cypherpunk’s Manifesto, Timothy May, Len Sassaman.