Why does privacy matter?

Pick the thread back up

The Zcash page showed what shielding does: a fully shielded payment hides who sent it, who received it, and how much moved, while a transparent chain — like Bitcoin — publishes all three for anyone to read, and keeps them forever. That page also left an honest caveat: the strong version of that privacy only holds if you actually use it, and stay shielded end to end.

This page answers the question the last one assumed: why bother? The common reaction to financial privacy is "I have nothing to hide" — privacy sounds like something only criminals need. The answer turns on one idea that most people miss, and it is worth stating before any example: privacy is not secrecy. The thing that exposes you on a public ledger is usually not the content of a single payment. It is the pattern.

Privacy is about patterns, not secrets

The data about your activity — who you deal with, when, how much, how often, in what order — has a name: metadata. It is everything except the contents. And the lesson of the last decade is that metadata, on its own, is enough to identify people and infer the most sensitive facts about them, even when the contents stay sealed.

That is not a hunch. When researchers at Stanford studied ordinary telephone metadata — just the records of which number called which, and when, never the conversations — they found it "is densely interconnected, susceptible to reidentification, and enables highly sensitive inferences," from medical conditions to relationships, in Evaluating the privacy properties of telephone metadata (PNAS, 2016). The people whose job is surveillance have long known this. In a 2014 debate at Johns Hopkins, the former director of the NSA and CIA, Michael Hayden, put it bluntly: "We kill people based on metadata." The point is not the drama of the line; it is that the patterns around a message can matter more than the message.

A blockchain is made of metadata

Now look at a transparent blockchain with that idea in hand. Every payment records an amount, a time, and which address paid which — and all of it is public and permanent. That is metadata, published by design. So a transparent address is not anonymous; it is pseudonymous, a stable name you simply have not attached to a person yet.

Attaching it turns out to be routine. In A Fistful of Bitcoins (2013), researchers grouped Bitcoin addresses into wallets using simple heuristics about how transactions are built, then tied those clusters to real services and people by transacting with them. Their summary of Bitcoin's privacy is exact: ownership is "implicitly anonymous," but the flow of money "is globally visible." Link one address to you a single time — through an exchange that knows your name, a refund, a posted donation address — and the public graph unwinds in both directions: where the money came from, where it went, and how much you hold.

Why this matters for ordinary people

Which brings back "I have nothing to hide." The objection treats privacy as a defence for wrongdoing. The record suggests a plainer reading: a public balance attached to a real person is simply a target, and the consequences are not hypothetical.

Jameson Lopp maintains Known Physical Bitcoin Attacks, a public, continuously updated catalogue — compiled from news reports — of robberies, home invasions, kidnappings, and extortion aimed at identifiable cryptocurrency holders. It is not specific to Zcash, or to any one coin; it spans the whole space, and runs to hundreds of incidents recorded since 2014. The catalogue notes its own limit plainly: it is "not comprehensive," because many such attacks are never reported publicly. Read it as data, not as a verdict: it shows that being visibly identifiable as a holder of valuable, liquid, hard-to- recover money carries a physical risk — and that this risk lands on anyone exposed, not only on people with something to hide. What you make of that is yours to decide; this page only puts the evidence next to the claim.

What Zcash removes — and what it doesn't

This is the gap a shielded payment closes. Because a shielded-to-shielded transaction never writes the sender, the receiver, or the amount onto the chain, the metadata that chain analysis feeds on is simply not there to collect. There is no public balance to attach to your name and no flow to follow.

But shielding protects you only to the extent you use it, and the same caveat from the Zcash page is where people slip: whenever value crosses between the transparent and shielded sides, the chain always reveals the amount transferred. Privacy on Zcash is therefore not a switch that is simply on; it is a property you can keep or leak depending on how you move. That is the difference between having a private tool and staying private with it — and it is why the last idea on this page is practical.

Transaction hygiene: operational security for money

If amounts, timing, and reuse are metadata, then careless habits leak metadata even through a private system. Researchers showed exactly this for Zcash. In An Empirical Analysis of Anonymity in Zcash (USENIX Security, 2018), the authors found that "while it is possible to use Zcash in a private way, it is also possible to shrink its anonymity set considerably by developing simple heuristics based on identifiable patterns of usage." A few of those patterns are worth knowing, because avoiding them is entirely under your control:

The practical version is short. Keep value shielded rather than round-tripping it through transparent addresses; avoid moving the same distinctive amount in and out close in time; do not reuse addresses. None of this is exotic — it is just operational security (often shortened to opsec) applied to money: the same discipline, used by journalists and ordinary people as much as by anyone, of not leaving a pattern that ties your actions together.

The discipline reaches well beyond money, and it is worth learning on its own terms. Two free, well-maintained guides are good places to start: the EFF's Surveillance Self-Defense and Privacy Guides.

One layer down: the network

A last pointer, because privacy has layers. Shielding hides the payment on the ledger, but your payment still travels as packets across a network, and the timing and routing of those packets are themselves metadata — a watcher who cannot read your transaction may still see that your connection is the one that sent it. Two tools address that separate, network layer. Tor routes traffic so that a service's network location stays hidden; this site is published as a Tor onion service, reachable over that network without revealing where it runs. Mixnets (mix networks) go further: NYM, building on the Loopix research design, adds decoy traffic and deliberately delays and shuffles packets so that even an observer watching the whole network cannot match sender to receiver. Ledger-layer privacy (Zcash) and network-layer privacy (Tor, mixnets) are different problems; strong privacy wants both.

Sources