The privacy you actually have

The most durable misconception about bitcoin is that it is anonymous money for anonymous people. The truth is closer to the opposite: every transaction ever made is published, permanently, to anyone who wants to read it, and it stays readable forever. Cash is anonymous. Bitcoin is a public accounting record with nicknames.

That does not make privacy impossible. It makes it something you have to do deliberately, understanding what leaks and where — which is what this page is for.

1Pseudonymous, which is a different thing

Addresses are not names, and that is genuinely worth something. An observer scrolling the chain sees strings, not people.

But pseudonymity is brittle in a specific way: it holds perfectly until one link is made, and then it fails backwards through everything connected. Learn that one address is yours and the observer does not learn one fact about you — they learn every transaction that address ever took part in, every address linked to it, and every future move those coins make. Retroactively, permanently, with no way to withdraw the information.

Compare that with a bank, which knows everything about you but shows the world nothing. Bitcoin inverts it: the world sees everything and initially knows nothing about who you are. The whole game is keeping the second half true.

2What one ordinary payment gives away

Before any surveillance industry gets involved, look at what falls out of a completely normal transaction.

Two inferences did all that work, and both are just reasoning about amounts:

• Common input ownership. If a transaction spends several coins at once, one person almost certainly controlled all of them — you need every private key to sign. This is the single most powerful heuristic in chain analysis, and it merges your coins' histories into one identity every time you combine them.
• Change detection. Payments tend to be round; change is the leftover. Add supporting signals — the change often returns to the same address type as the inputs, while the payment may not — and following your money forward becomes reliable rather than speculative.

Chain analysis firms sell sophistication on top of this, but the foundations are these two observations applied at scale. Nobody needed to hack anything.

3Where your name gets attached

The ledger has no identities in it. They come from outside, at a small number of predictable points.

• Regulated exchanges. You verified your identity, then withdrew to an address. That address is now documented as yours, and the analysis spreads outward from it. This is the most common entry point by a wide margin.
• Address reuse. Publishing one address that receives repeatedly — a donation address, a shop's payment address — creates a permanent, public dossier of everything it ever received.
• Paying identified counterparties. Every merchant, service, or friend who knows your name also learns an address of yours.
• Your wallet's server. Covered in why run a node, and worth repeating: a wallet with no node hands your address set and your IP to somebody else's machine.
• Block explorer lookups. Checking your own transaction on a public explorer tells that explorer which transaction you care about, from your IP address.

4What actually helps

Roughly in order of benefit per unit of effort. The first three are the ones that matter for almost everybody.

• Never reuse an address. A fresh one for every payment, always. Wallets do this automatically if you let them; the harm comes from pasting a saved address repeatedly.
• Run your own node. The largest single improvement available. It closes the xpub leak, the address-query leak, and the IP correlation in one step.
• Keep coins from different sources apart. Coins from a KYC exchange and coins from a private sale should not be spent together, because doing so publicly declares one owner. This is what coin control is for — see coin control in Sparrow.
• Label everything as it arrives. You cannot avoid combining coins carelessly if you cannot remember where any of them came from. Labels are a privacy tool, not bookkeeping.
• Route over Tor where your wallet supports it, so your IP is not attached to your broadcasts and queries.
• Think before consolidating. Merging many coins when fees are low is good fee strategy and bad privacy — it announces common ownership of everything merged. Consolidate within a context, not across.

CoinJoin, briefly

A CoinJoin builds one transaction with many participants and many equal-sized outputs, so an observer cannot tell which output belongs to which contributor. It genuinely breaks the input-ownership heuristic, which is the strongest tool used against you.

It is also not a cleaning service. Coins carry their visible history before and after; what changes is that a specific link becomes ambiguous. Some exchanges treat CoinJoined coins with suspicion, the coordinator landscape has repeatedly proven unstable, and doing it badly — consolidating the outputs afterwards, for instance — can undo the benefit entirely. Worth understanding properly before using, rather than as a reflex.

5Layer two, and what it changes

The obvious question is whether moving off the main chain fixes any of this. Partly, and with real caveats.

Lightning

Lightning payments happen between participants who have locked funds into a shared channel, and the individual payments are not published to the chain. That is a substantial and genuine improvement — a hundred Lightning payments leave no hundred entries in a public ledger for anyone to analyse later. Payments are also onion-routed, so an intermediate node forwarding your payment does not learn who sent it or who ultimately receives it.

What it does not do:

• Opening and closing a channel is an on-chain transaction, with all the usual analysis applying. Your entry into and exit from Lightning is public, including the amount you committed.
• Your channel partner sees your activity. They necessarily know the payments passing through your shared channel and how the balance moves.
• Forwarding nodes see amounts passing through them, and can infer more when they sit at both ends of a route or when payments are distinctive in size.
• Announced channels are public. Nodes advertising themselves for routing publish their channels, capacities, and partners. Unannounced channels avoid this at the cost of being unroutable to.
• Custodial Lightning wallets see everything, because they are simply holding your money and doing the Lightning part for you. Convenient, and not self-custody.

Net: Lightning is a real privacy gain for the payments themselves, and no help at all for the on-chain footprint at either end.

Liquid and the sidechain approach

Liquid takes a different angle: transactions on it use Confidential Transactions, so the amounts are cryptographically hidden while still being publicly verifiable as balanced. That is something the main chain simply cannot do — on bitcoin, every amount is in the clear.

The price is the trust model. Liquid is operated by a federation of known businesses who collectively control the peg holding the bitcoin. That is a materially weaker arrangement than bitcoin's, and it should be evaluated as such rather than treated as a free upgrade.

Newer designs

Statechains, Ark and similar constructions each rearrange the trade-offs — typically improving on-chain footprint or interactivity, each with their own assumptions about who must be online, who can censor, and what happens if a participant vanishes. They are worth watching and, as of now, worth understanding thoroughly before trusting with meaningful amounts.

6Being realistic about it

Two failure modes are common, and they are opposite.

The first is assuming privacy you do not have — treating bitcoin as untraceable and being surprised when an exchange asks pointed questions about the origin of a deposit. The chain remembers everything, and the analysis industry is mature and well funded.

The second is chasing perfect privacy and making everything worse. Elaborate schemes carry real risks: exotic wallet configurations you cannot restore, coins stranded in tools that stop being maintained, and self-inflicted losses that cost more than the surveillance ever would.

Privacy is a practice, not a product. The unglamorous habits — fresh addresses, your own node, coins kept apart, everything labelled — outperform anything you can buy or install.

And be clear about the threat you are addressing. Keeping your net worth off a public ledger that your neighbours, colleagues and potential burglars can read is an entirely ordinary thing to want, and it is what these practices achieve. That is a different goal from evading a determined state adversary, which is not a problem a wallet setting solves.

The short version

Every transaction is public forever. Addresses are pseudonyms that fail backwards the moment one is linked to you, and the linking is done mostly with two pieces of arithmetic: coins spent together share an owner, and the uneven output is the change. Identity enters at exchanges and at reuse. Lightning genuinely hides individual payments and does nothing for the on-chain footprint at either end.