MSTR Cat

Blockchain/Level X · Full circle/10.3 Living on bitcoin/Lesson 3

Privacy on the way back

Identity trails, coin selection, and the link between privacy and physical safety

MaterialsA full node running Bitcoin Core or equivalent softwareA self-custodial wallet with coin control enabled (e.g., Sparrow Wallet, Bitcoin Core GUI)Access to a blockchain explorer that visualizes address clustering (e.g., mempool.space)

Wonder

  1. How does a single transaction input reveal that two unrelated addresses belong to the same person?
  2. What specific mechanism allows a user to separate coins from different sources without merging their histories?
  3. Why is maintaining address separation considered a form of physical security rather than just data hygiene?

Explore

  1. Bitcoin transactions are public records. The Common Input Ownership Heuristic (CIOH) assumes that all inputs in a single transaction belong to the same entity. When coins from distinct sources—such as a KYC exchange and a peer-to-peer trade—are combined into one input set, an observer links those addresses permanently. This clustering propagates: every future output touched by these linked addresses inherits the connection, creating a dense graph of identity associated with specific UTXOs.
  2. Labels record where each coin came from, and BIP 329 defines a standard export format so those labels move between wallets. Combined with coin control—a feature in wallets like Sparrow or Bitcoin Core—users can manually select specific UTXOs for spending. This prevents the automatic consolidation of inputs from disparate origins, breaking the link that CIOH would otherwise infer. The practice requires active management; wallets default to merging for fee efficiency unless overridden.
  3. Address reuse is a critical failure mode. Using the same address for multiple deposits or withdrawals allows observers to sum all associated transactions and attribute them to a single entity. Even if inputs are kept separate, reusing an output address links new funds to old ones. Best practice involves generating fresh addresses for every interaction, ensuring that no two distinct economic activities share a public identifier on the blockchain.
  4. Privacy tools extend beyond basic wallet settings. PayJoin (BIP 78) has the receiver add one of their own inputs to the sender’s payment, so the transaction’s inputs no longer belong to one owner and the amount paid is hidden; it works only when the receiver’s wallet supports it. More fundamentally, running a full node ensures that transaction construction does not leak address associations to third-party servers via API calls, keeping the local wallet’s data private from infrastructure providers.
  5. The stakes of privacy extend beyond financial anonymity; they encompass physical safety. If an observer can link addresses to a known identity and determine total holdings, they possess leverage for extortion or theft. Keeping holdings private is a defensive measure against targeted attacks. Jameson Lopp’s public list of physical attacks on bitcoin holders shows how often visible wealth precedes a robbery.
  6. On a block explorer, open any transaction with several inputs: explorers and analytics firms treat all of them as belonging to one owner. Then open a wallet with labels and coin control, such as Sparrow on signet, and list which coins could be spent together without linking sources that should stay apart.

Key facts

  • The Common Input Ownership Heuristic (CIOH) links all inputs of a transaction to a single owner, permanently clustering distinct sources.
  • BIP 329 defines a standard format for exporting wallet labels, so the record of where each coin came from moves between wallets.
  • Coin control allows users to manually select specific UTXOs for spending, preventing the automatic merging of inputs that would trigger CIOH linkage.
  • Address reuse links new transactions to historical ones, allowing observers to aggregate all activity associated with a single address into one identity profile.
  • Running a full node prevents third-party servers from learning which addresses belong to the user during transaction construction and broadcasting.
  • Privacy practices are physically protective; linking an identity to large on-chain holdings increases vulnerability to extortion and targeted theft.

Exercise nine, six, three, one

9CollectList 9 distinct sources of bitcoin funds (e.g., KYC exchange, P2P trade, mining reward, Lightning channel closure). For each, note the inherent identity linkage risk when that source is first touched by a wallet.
6ClusterGroup the 9 sources into 6 categories based on their initial privacy state: fully identified, partially identified, pseudonymous but linkable, unlinked, mixed-source, or high-risk consolidation candidates.
3DistillReduce the 6 groups to 3 core principles for managing UTXO provenance: isolation of sources, address hygiene, and active coin selection.
1CrystallizeWrite 1 sentence explaining why a wallet that automatically consolidates inputs is structurally hostile to privacy regardless of its other features.

Fact check

Dates, figures and claims checked against the published sources listed below.

Open in the interactive academy →

PT ES ZH JA KO RU DE FR MS