Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.
A statement of purpose, not a technical spec
Eric Hughes published 'A Cypherpunk's Manifesto' on 9 March 1993. It is a short political document, not a protocol: it specifies no algorithm, currency or network. Its central claim is a distinction rather than a design — privacy, the manifesto says, 'is the power to selectively reveal oneself to the world', which it separates from secrecy, hiding that a thing happened at all. The text argues people should be able to disclose only what a given transaction requires, and no more, and that cryptography, not institutional promise, is the durable way to arrange that.
What the manifesto asks a payment system to do
The manifesto states that 'privacy in an open society requires anonymous transaction systems', with each party holding 'knowledge only of that which is directly necessary for that transaction'. That is a functional requirement: a payment should reveal an amount and a settlement, and little else about the parties. It predates any working cryptographic payment network by years, and it sits in the same territory as David Chaum's earlier work on blind signatures, without adopting Chaum's issuer-based architecture. The manifesto demands a property; it is not a proof that any particular design supplies one.
Measuring a public ledger against that demand
Bitcoin answers part of the brief and misses another part. The whitepaper keeps identities off public keys, so a payment does not by itself carry a name. But the transaction itself stays permanently visible: amounts, timing and the graph connecting addresses are public, closer to the stock-exchange 'tape' the paper compares itself to than to Hughes's 'knowledge only of that which is directly necessary'. Once one address is linked to an identity, through an exchange, a leak or an investigation, the connected history becomes attributable. A public, permanent ledger is a specific and unusual kind of transparency the 1993 text does not anticipate in its own terms.
The gap between a goal and a delivered property
None of this makes the manifesto's programme obsolete or the ledger's design a failure on its own terms; the two documents answer different questions, written fifteen years apart, and neither should be read as a review of the other. What the pairing does establish is that privacy in this literature has never meant one single thing, and a system deserves judgement against the specific disclosure it promises, not against the word alone.
- Does a system hide who transacted, what was transacted, or only when it happened?
- What happens to past transactions once one address in the graph is identified?
- Is the claimed privacy a property of the protocol, or of a wallet practice layered on top of it?
Read as a design brief rather than a manifesto, the 1993 text is still a useful checklist against which to measure any later claim about what a ledger conceals.
Sources & reading trail
States the manifesto's date and author and its definition of privacy as selective disclosure, distinct from secrecy.
Source published: 9 March 1993 · Retrieved: 16 September 2026
Shows the earlier, issuer-based approach to selective disclosure that the manifesto's demand does not itself specify.
Source published: Not established · Retrieved: 16 September 2026
Shows what the ledger keeps public, including amounts and the transaction graph, against which the manifesto's demand is measured.
Source published: Not established · Retrieved: 16 September 2026
Historical sources establish the record; the questions and interpretation are Block Due Diligence’s editorial analysis. This retrospective draft does not imply the site published on the event date.