Privacy & Analysis
Anonymous vs pseudonymous: what Bitcoin actually records
Protocol referenceSource: Bitcoin.org, Protect your privacyNo market data is used on this page; the definitions follow the protocol documentation and published clustering research.
Two different claims
Anonymity means that an action cannot be attributed to a person even in principle. Pseudonymity means that an action is attributed to a stable identifier, but the link between that identifier and a person is not published by the system itself. Bitcoin is pseudonymous in the second sense and not anonymous in the first. A transaction names inputs and outputs by script, not by name, and nothing in the protocol requires a participant to reveal who they are. But every transaction is broadcast to every node, stored forever, and readable by anyone, so the identifier a payment touches accumulates a history that no participant can later erase.
The confusion usually comes from treating those two properties as a single scale. They are independent. A system can be anonymous without being private — a one-time payment that anyone can watch arrive is anonymous to the observer but not private in any useful sense. A system can be private without being anonymous — a bank transfer is fully attributed to named accounts and yet the amounts and counterparties are not public. Bitcoin sits in a third position: the identifiers are not names, but the record attached to them is complete, and the question of whether a given identifier belongs to a person is answered by information outside the protocol.
That last point is the one that matters in practice. The protocol does not leak identity, because it never holds identity to leak. What it does is preserve a perfect audit trail of behaviour, and behaviour is what links an identifier to a person. An exchange that records a withdrawal address, a merchant that ships to an address, a forum post that publishes a donation address — each of these is an off-chain fact, and each one converts a pseudonym into a name. The ledger cannot be edited to undo that conversion.
What linkability means
Linkability is the property that two identifiers belong to the same party. Bitcoin does not publish that fact, but it publishes enough structure for an observer to infer it. The best-known inference is the common-input-ownership heuristic: when a transaction spends several outputs as inputs, the observer assumes that one party controls all of them, because producing the signatures requires the keys for every input. That assumption is not a protocol rule and it is not always true — a collaborative transaction such as a CoinJoin deliberately spends inputs from several parties — but it is true often enough that it forms the basis of commercial chain analysis.
Once two identifiers are linked, the link is transitive in the observer's model. If address A is linked to address B by one transaction and B is linked to C by another, the observer treats A, B and C as one cluster, and every payment any of them makes is attributed to that cluster. The cluster is not a person, but it is a behavioural unit, and it is the unit that analysis firms sell. A single careless transaction can therefore merge two sets of holdings that the owner had deliberately kept apart, and the merge is permanent.
Linkability is also what makes the distinction between anonymity and pseudonymity concrete rather than philosophical. If a cluster is never connected to a person, the pseudonym has held. If it is connected once — through a withdrawal, a purchase, a published address — then every transaction in the cluster is connected, not just the one that made the link. The tracing page sets out the heuristics in detail, and the limits of analysis page covers where the inference breaks down.
Where the distinction is routinely misstated
The first common error is to treat "no names on the ledger" as anonymity. It is not, because the ledger is not the only source of information. An observer who can match one address to a person can read the rest of the cluster, and the matching is often trivial: exchanges are regulated, merchants keep records, and addresses are frequently published on purpose. The protocol's silence about identity is a design property, not a guarantee about the world around it.
The second error runs the other way and treats Bitcoin as fully traceable. That overstates the case. The heuristics are probabilistic and they produce false positives; mixing, custodial flows and off-chain settlement all break the chain of inference; and a cluster that is never linked to a person remains a set of pseudonyms. The honest position is that Bitcoin is transparent by default and that privacy is achievable through deliberate practice, not that it is either guaranteed or impossible.
The third error is to assume that a fresh address is a fresh identity. Addresses are free and unlimited, but they are not independent: a wallet that spends two of them together has published the link, and a wallet that derives them in sequence from one seed has published a structure that an observer can sometimes exploit. The address reuse and change addresses pages take each of those cases in turn.
Sources
- Bitcoin.org, Protect your privacy — the project's own statement that transactions are public, traceable and permanently stored, and that addresses should be used once.
- Bitcoin Core, Privacy features — the reference implementation's account of pseudonymous transactions and what a wallet can do about them.
- Loporchio, Bernasconi, Di Francesco Maesa and Ricci, Is Bitcoin gathering dust? — Applied Network Science, 2023; states the pseudonymity property and the multi-input heuristic used to break it.
Related reading
- Privacy & AnalysisWhat the public ledger reveals, and the practices that change it.
- How Transactions Are TracedThe heuristics chain analysis applies, and where they break down.
- Address ReuseWhy reusing an address links every payment to it, and what wallets do instead.
- Coin ControlHow choosing which outputs to spend changes what an observer can infer.
- Change AddressesWhy a transaction sends value back to the sender, and how change is identified.
- Transaction BatchingHow combining payments lowers the fee per payment, and what it reveals.