Protecting Bitcoin Privacy After Address Disclosure

Once a Bitcoin address is disclosed, it cannot be retracted or reissued like a compromised bank account, as its transaction history is permanently etched on the public blockchain. If a third party, such as an exchange or observer, has linked that address to its owner, it becomes impossible to eliminate that connection retroactively.

Transferring assets to a new wallet does not resolve the issue, as the transaction history remains traceable. Consolidating funds from various previous addresses into a new one exacerbates the problem, as analysts can associate the entire balance with the owner.

In partnership with Mixer.Money, we delve into what the blockchain reveals, strategies for segregating savings by source, and the costs of disconnecting from previous transaction histories.

One Transaction Compounds Risk

Bitcoin wallets typically show a total balance, but the system relies on unspent transaction outputs (UTXO), akin to banknotes of various denominations representing available funds. Each UTXO must be fully utilized in transactions. For example, if a payment of 0.15 BTC is required, a wallet might use a 0.40 BTC output, resulting in two new outputs: one for the recipient and the other returned to the owner as change, minus network fees. If the needed amount surpasses any single output, multiple outputs will be utilized.

This principle follows the Common Input Ownership Heuristic, which assumes that if outputs are spent together, they are controlled by one entity, thus clustering those outputs for analysis.

For instance, consider four UTXOs from different sources: 0.40 BTC from a KYC exchange, 0.15 BTC from a P2P transaction, 0.20 BTC from a mining pool, and 0.05 BTC as a gift. If an observer has linked only one address to a specific person, the histories remain distinct until all are included in a single transaction.

Sweeping the entire balance at once, which clusters the outputs, risks exposing the owner’s entire profile by merging P2P transactions, mining income, and gifts.

Separate and Avoid Mixing

A sweep represents an extreme scenario. By default, wallets select inputs without considering the origins of the coins, leading to merged transaction histories even in routine payments. Therefore, it’s crucial to evaluate existing connections before sending coins. Here are essential steps:

1. Cease using the exposed address. Update advertisements, invoices, and communication with regular contacts. For permanent public payments, consider employing silent payments, which allow for unique on-chain outputs for each transaction.
2. Create a UTXO registry. Document the source of each output using wallets that support transaction tagging and manual coin selection, like Sparrow Wallet.
3. Separate outputs into distinct domains. A domain includes UTXOs known to a particular observer group. For example, two outputs from a KYC exchange belong to the same domain, and coins from friends or P2P transactions should not be mixed with exchange outputs.

Labeling does not erase previous overlaps but prevents new ones from forming, aiming to avoid expanding the disclosed cluster with additional coins.

Two Methods to Sever Connections

For basic privacy, refrain from reusing addresses and avoid combining different domains in a single transaction. However, if you need to detach exposed outputs from their history, anonymization services are available.

The first method is CoinJoin, which merges inputs and outputs from multiple participants in a single transaction, complicating the ability to tie them back to individuals. However, this method has a recognizable structure that can attract scrutiny from centralized exchanges.

The second method involves using a Bitcoin mixer like Mixer.Money, which breaks down incoming funds and redistributes them among private traders, thus severing the direct link between the incoming transfer and the payout.

Testing the "Full Anonymity" mode can be effective. However, successful outcomes depend on thorough preparation, including planning receiving addresses and domain breakdowns before submission. Key steps include:

1. Test the service with a small amount. Sending 0.001 BTC is fee-free, allowing users to understand the process before larger transfers.
2. Prepare receiving addresses. Specifying up to two addresses improves mixing quality, ideally selecting addresses with no shared history.
3. Submit the request. No registration is needed; the form provides an address for sending, a QR code, and a cost estimate, valid for seven days.
4. Save the guarantee letter. This document, signed with a PGP key, verifies addresses, fees, and mixing time.
5. Send the domain in one transaction. Processing starts after the first confirmation in the Bitcoin network.
6. Await the payout. Coins will arrive in parts, indicating an ongoing process rather than a failure if the balance is incomplete.

Users must relinquish some control, as the system determines payout timing and distribution. Effective domain separation requires distinct transactions for each domain using separate receiving addresses.

***

Once recorded, blockchain history cannot be erased. The realistic goal is to retire the exposed address and prevent further expansion of the established cluster. Begin by assessing UTXOs and deciding which coins to anonymize. After mixing, domains must remain separate to avoid consolidation through common transactions or KYC accounts.