21wiki

Privacy

4 min read

Privacy

Tags: privacy, coinjoin, surveillance, fungibility, on-chain

Why Bitcoin Privacy Matters

Bitcoin’s ledger is fully public — every transaction is visible to anyone. This is necessary for the consensus mechanism but creates surveillance risks:

  • Address clusters can be linked to identities (via KYC at exchanges, IP addresses, merchant data)
  • Once an identity is linked to an address, the entire transaction history becomes deanonymized
  • Governments and blockchain analysis firms (Chainalysis, Elliptic) actively perform this surveillance
  • “Tainted” coins can be blacklisted by exchanges, threatening fungibility

Privacy is not about hiding illegal activity — it is the foundation of financial sovereignty.

Source: raw/Theory/privacy/, raw/Theory/privacy/oxt/, raw/Theory/philosophy/cypherpunks-manifesto.md

Fungibility Problem

Bitcoin’s fungibility is theoretical but practically compromised. If exchanges can blacklist “tainted” coins, then not all bitcoins are equal — which breaks a fundamental property of money. CoinJoin and privacy tools are not luxuries; they restore fungibility.

Source: raw/Theory/privacy/bitcoin-fungibility.md

KYC vs. No-KYC

KYC (Know Your Customer): exchanges and services that collect identity documents. Problems:

  • Permanent data: your identity is permanently linked to your bitcoin addresses
  • Data leaks: exchange databases are hacked regularly
  • Government coercion: exchanges are compelled to report/freeze funds
  • Address surveillance: all future transactions from those addresses are tracked

No-KYC acquisition:

  • P2P exchanges: Hodl Hodl, RoboSats, Bisq
  • ATMs (small amounts, higher fees)
  • Mining, earning, accepting payment

Source: raw/Theory/privacy/no-kyc.md

Blockchain Analysis Techniques

From the OXT Research series (Samourai Wallet team):

CIOH (Common Input Ownership Heuristic): If multiple inputs appear in the same transaction, they likely come from the same wallet. This allows clustering addresses into entities.

Change detection: When a transaction has two outputs, one is typically change back to the sender. Analysts use value patterns, address reuse, and address types to identify the change output.

Transaction graph analysis: Following the flow of coins through multiple hops.

Source: raw/Theory/privacy/oxt/

CoinJoin / Whirlpool

CoinJoin merges multiple users’ inputs in a single transaction with equal-value outputs, making input-output linking impossible. The equal outputs defeat the CIOH heuristic.

Whirlpool (Samourai Wallet implementation):

  • 5 equal-output pools (100k, 1M, 5M, 50M satoshis)
  • ZeroLink protocol: fresh UTXOs, no post-mix address reuse
  • Pre-mix and post-mix UTXO management
  • “Toxic change” concept: unequal change from pre-mix stays pre-mix

Note: Samourai Wallet developers (Keonne Rodriguez and William Hill) were arrested by the DOJ in April 2024. The wallet is still functional. See raw/Theory/privacy/freesamourai.md.

Source: raw/Theory/privacy/coinjoin.md

BIP47 / PayNym

BIP47 introduces reusable payment codes. Alice generates a payment code; Bob generates a derived address for each payment from Alice using ECDH. This eliminates address reuse (a privacy leak) while enabling a recognizable “identity” (PayNym contact). Samourai Wallet implements this as PayNym contacts.

Source: raw/Theory/privacy/bip47-the-ugly-duckling.md

Lightning and Privacy

Lightning offers better privacy than on-chain (payments are not publicly broadcast) but has issues:

  • Public channel graph reveals node topology
  • Routing nodes see payment paths they participate in
  • Payment probing can map balances

Improvements: private (unannounced) channels, onion routing (already used in Lightning), Blinded Paths (BOLT12).

Source: raw/Theory/lightning/lightning-privacy.md

Privacy Tools Stack

LayerToolPurpose
AcquisitionRoboSats, Hodl Hodl, BisqNo-KYC BTC purchase
On-chain mixingWhirlpool (Samourai)CoinJoin to break history
Wallet backendDojo / RoninDojoSelf-hosted node so wallet doesn’t leak to third-party server
Mobile OSGrapheneOSHardened Android, no Google tracking
Self-hosted nodeBitcoin Core + ElectrsVerify your own blocks, no reliance on third-party nodes
LightningPhoenix, MutinySelf-custodial LN with LSP handling liquidity

Dojo (Self-Hosted Samourai Backend)

Dojo is the node backend for Samourai Wallet. Without it, Samourai’s servers see your addresses and transaction history. With Dojo, your wallet connects to your own node — Samourai learns nothing.

RoninDojo = Dojo packaged for x86 hardware with GUI, Whirlpool integration, and Electrum Rust Server.

The Dojo series (7 parts, raw/Practice/privacy/dojo/) covers the complete setup.

Source: raw/Practice/privacy/ronindojo.md, raw/Practice/privacy/dojo/

GrapheneOS

GrapheneOS is a hardened Android OS for Pixel phones. It removes Google Play Services, sandboxes apps, and hardens the OS against exploitation. Recommended for maximum privacy on mobile Bitcoin/Lightning use.

Source: raw/Practice/privacy/grapheneos.md

Sources

Synthesized from multiple sources in the /raw/privacy directory https://21ideas.org/privacy/. No single canonical source article.

Glossary | Bitcoin | UTXO | self-custody | Lightning Network | blockchain analysis | privacy practice | cypherpunks | no-KYC buying

Graph View

Backlinks