Full article
An unnamed address can still become identifiable
Bitcoin.org’s privacy guide explains why public transactions and pseudonymous addresses can coexist. The absence of a name field does not establish that observers can never identify the person involved. Think of an address as a publicly used identifier. On its own it may reveal little about identity; placed beside an order, donation page, or named post, it gains another relationship. Privacy therefore depends not only on the structure of blockchain data but also on information shared elsewhere and on which parties can bring those separate pieces together.
Repeated use accumulates context
Imagine a freelance worker placing the same receiving address on every publicly visible invoice. Payments from different clients then gather around one identifier. An observer may still misunderstand individual transactions, but has more material for guesses about timing and business relationships. This is a hypothetical teaching example, not a description of an identified person. Different receiving addresses can reduce this straightforward link without making every payment permanently independent. Later activity or outside information may provide new ways to associate records that initially appeared separate. Reducing one connection is not the same as removing every possible connection.
Proof of payment can disclose more than the payment
Suppose two parties need only to establish that an expected payment arrived. The recipient instead posts a complete transaction screenshot publicly. It may reveal timing, addresses, and other details useful for comparison, alongside the fact of receipt. The issue is not whether the information is true, but whether meeting one purpose also discloses more than necessary. Our analysis separates proving receipt from publishing a transaction’s wider context. Even when the underlying data is already searchable, attaching a name can materially change how easily another person can find and interpret it.
Separate purposes do not create an absolute barrier
Using different wallets for different purposes can organize records and everyday sharing, but it is not an anonymity guarantee. Imagine someone separating personal and business activity, then publicly identifying both addresses as their own. The interface separation cannot undo that disclosure. Observers also differ: a casual reader, a transaction counterparty, and a service holding account information do not necessarily have the same visibility. A privacy measure therefore needs a defined objective: what information should be less available, and to whom? A single unexplained privacy score cannot express those differences.
Later disclosure can change the meaning of old records
Persistent public records allow newly available information to change the interpretation of earlier activity. Imagine an address remaining unidentified for years before a public document links it to a person. Previous associated records may then become easier to interpret. That does not make every inference accurate; it describes how stored information and new clues interact over time. Our conclusion is that reducing unnecessary links is a more useful goal than expecting one action to establish permanent anonymity. The visible transaction history remains, even when a particular practice makes some relationships harder to infer.