Pseudonymity

Anna writes a blog under the name North Star. Readers recognize her posts without necessarily knowing her real name. A Bitcoin address can work in a similar way: people recognize payments associated with an identifier that contains no legal name. This is pseudonymity. Anna adds a donation address to her blog. A reader can now follow receipts at that address; if Anna later links the blog to her name, the already visible history gains another connection. Nobody has broken any encryption. A new piece of information has joined two things that were previously separate. The Bitcoin Whitepaper already warns that exposing one connection can help identify other transactions. [1] [2]

A Bitcoin address tells the wallet how to set the spending conditions for a new transaction output. It is neither a person's registration nor an identity document number. An output records an amount and the conditions for spending it. Anna can use many addresses, and several people can manage a shared wallet. A private key is secret data that a wallet uses to make a digital signature authorizing a payment. A Public Key lets others verify digital signatures, not the signer's surname. A valid signature demonstrates use of the corresponding private key; by itself it cannot distinguish Anna from a custodian or a thief who obtained that key. Control over funds and legal identity are therefore different questions. [4]

If Anna also uses her blog address on business invoices, she connects two parts of her life herself. Readers can see other receipts at the same address, although they may not know which was a donation and which came from a customer. A fresh receiving address for each payment limits this straightforward connection. A typical wallet can generate many addresses without opening a new account and usually manages them under the same backup. A new address is not a new identity with guaranteed anonymity, though. Other clues may show that different addresses are used by the same person. [2]

Suppose Anna buys bitcoin on an exchange that has checked her identity through KYC. The exchange knows her account and the address she supplied for a withdrawal. The withdrawal alone does not prove she controls the destination: she may have sent the money to someone else. But the exchange has a specific connection that a casual blog reader lacks. A merchant knows the order and perhaps a delivery address. These details are not automatically written into the Bitcoin transaction or made public to everyone. They can nevertheless add context to its public record. Privacy must therefore be assessed against a particular observer and what that observer actually knows. [2]

Bitcoin does not debit and credit accounts held in people’s names. A payment spends earlier unspent outputs, called UTXO, and creates new ones. Their amounts and connections are public. An observer can see real links between transactions while still having to infer which people control the different parts. That distinction matters: a public history of value moving is not a ready-made list of owners. A name added later may shed new light on payments made long ago. Removing an address from a blog does not erase old transactions and may not remove saved copies of the blog either. [1] [4]

A wallet sometimes pays by combining several UTXO and sends the excess back to an address it controls as change. An analyst may assume the combined inputs belong to one owner and estimate which output is change. This produces groups of addresses thought to be related. These methods are heuristics: useful inferences rather than proof of identity. CoinJoin and PayJoin, for example, allow multiple participants to contribute to a transaction. Even a convincing-looking address map therefore does not establish that Anna controls every address in it. The strength of that conclusion depends on other evidence. [6]

Anna wants to view her wallet in another application and exports an XPUB, an extended public key. BIP 32 organizes keys into branches like a tree. An XPUB can be used to calculate further public keys in its branch, but not across a hardened derivation step: that step requires a private key. With the required address-type information, the application can then track related payments. An XPUB alone cannot sign spending transactions, yet it can expose past and future activity in that branch. It does not automatically reveal every wallet or account derived from the same backup. It still provides a much broader view than a single address given to a customer. [3]

When Anna looks up her address on a web explorer, its operator may connect the query to her IP address, a network connection identifier, or to a signed-in account. The server her wallet uses to retrieve its history may gather similar information. These operational details are separate from the public blockchain, but can help connect its records to a person. A Full Node is a computer running software that independently checks Bitcoin transactions and blocks against the network’s rules. Running a Full Node reduces the queries sent to someone else's server if the wallet actually uses that node. Tor can reduce IP address exposure; it cannot remove an already published connection between a blog and a payment. [2]

A Lightning Network payment is generally not written to the public blockchain as a separate transaction. That removes one visible trace, but does not mean nobody knows anything about the payment. A Lightning node is software that manages payment channels: connections in which two parties update how their committed funds are divided. A node uses a public key as its identifier and can announce its public channels to the network. A BOLT 11 payment request lets the recipient's node identifier be determined; it may also contain other payment details and information about the route to the recipient. Sender, recipient and service provider hold different information. Publishing the request can reveal some of it to other people even though the payment itself takes place off the main chain. [5] [7]

Before Anna publishes an address or lets an application view her history, she can ask a simple question: who will be able to connect which pieces of information? Using new addresses for individual payments, knowing who receives an XPUB and understanding where the wallet gets its data all help. None of these steps alone promises complete anonymity, and a new setting does not erase old connections. The aim is to share less unnecessary information and understand which links already exist. That is more useful than assuming a long string of characters can hide a person by itself. [2] [3]