Public blockchains do not provide anonymity merely because an address omits a legal name. They provide a durable transaction record that can be combined with exchange records, merchant data, network information and a user’s own disclosures. Privacy therefore begins with an accurate threat model, not a promise to become “untraceable.”
1. Identify what must remain private—and from whom
A public donation address, a salary payment and a transfer between personal wallets expose different information. Decide whether the concern is a counterparty seeing a balance, a data broker linking purchases, a network observer identifying an IP address or a stolen device revealing account history. No single tool covers all of those risks.
2. Do not reuse receiving addresses
As our guide to public keys and Bitcoin addresses explains, an address is payment-routing information rather than an identity. Reuse nevertheless makes separate payments easier to associate. Bitcoin.org’s privacy guidance recommends generating a new address for each payment. Modern wallets normally do this automatically, including separate change addresses. Reuse may still be necessary for a public donation endpoint, but the resulting history should be treated as public.
3. Avoid combining identities through wallet behaviour
Spending outputs from several addresses in one transaction can provide evidence that a common wallet controls them. Labels and coin-control features help users avoid mixing unrelated sources, although using advanced controls incorrectly can create new fingerprints or fees. A fresh address does not help if later spending recombines everything.
4. Limit what services learn
A custodial exchange can associate deposits and withdrawals with a verified account. A hosted block explorer sees search queries; a wallet backend may learn all requested addresses; a portfolio tracker can assemble a complete balance. Share an address or extended public key only when the recipient needs it, and understand the view it grants.
5. Protect network metadata
Broadcasting a transaction reveals network information to peers or infrastructure providers. Running a full node can reduce reliance on third-party address queries, but it introduces operational responsibilities. Privacy networks may conceal origin traffic, yet poor configuration, browser activity or account logins can reconnect an identity. Network privacy is not the same as on-chain privacy.
6. Treat privacy tools as systems with trade-offs
CoinJoin-style transactions, privacy-focused assets and shielded protocols use different techniques and trust assumptions. Evaluate liquidity, coordinator design, wallet implementation, fee visibility and the possibility that deposits or withdrawals receive additional compliance scrutiny. A tool may improve one layer while leaking information through another.
7. Stay within legal and reporting obligations
Financial privacy is a legitimate security goal; it does not cancel tax, sanctions or anti-money-laundering rules. Regulated virtual-asset service providers may be required to collect and transmit originator and beneficiary information. FATF describes those obligations in its risk-based guidance for virtual assets and service providers. Requirements vary by jurisdiction and transaction type.
Privacy without false certainty
Bitcoin Core notes that confirmed transactions are published for anyone to inspect. Privacy comes from preventing those records from being reliably connected to a person or to one another—not from hiding the ledger. Good practice reduces unnecessary exposure; it cannot guarantee that past activity will remain unlinkable as analytical methods and external datasets change.
