Bitcoin (BTC)
Bitcoin (BTC) offers no native transaction privacy: every transaction is permanently recorded on a globally readable public ledger, with sender addresses, recipient addresses, and amounts visible to any observer. However, a layered set of external privacy protocols and operational practices documented in open-source research can substantially increase privacy for Bitcoin users. This guide covers the most effective documented techniques for using BTC more privately, with links to resources and tools from the academic and open-source communities.
CoinJoin and Bitcoin Mixing Techniques
CoinJoin is the primary privacy enhancement protocol for Bitcoin, first proposed by Gregory Maxwell in 2013. The JoinMarket protocol (github.com/JoinMarket-Org) implements CoinJoin in a decentralised market structure where liquidity providers (makers) earn fees for participating in mix transactions with initiators (takers). This eliminates the custodial risk of centralised mixers.
Wasabi Wallet (wasabiwallet.io) implements WabiSabi, a more sophisticated CoinJoin protocol using cryptographic blind signatures to prevent the coordinator from linking inputs to outputs. Sparrow Wallet (sparrowwallet.com) implements both the JoinMarket protocol and Whirlpool (originally from the Samourai Wallet project). Both wallets can operate over Tor, reducing network-level metadata leakage.
Key limitations of CoinJoin: the equal-output requirement is visible on-chain (outputs of exactly equal denomination are a CoinJoin fingerprint); address reuse after a CoinJoin can unmix the privacy gain; and change outputs from CoinJoin transactions often remain attributable to the originating wallet. The Bitcoin Privacy wiki (bitcoin.it/wiki/Privacy) documents these limitations and the current best practices for mitigating them.
Lightning Network Privacy Considerations
The Lightning Network improves Bitcoin payment privacy in one dimension — off-chain payments do not appear on the base-layer blockchain — while introducing new privacy challenges in others. Payment routing information is propagated across the network's gossip protocol, and channel balance information can be inferred through probing attacks. Research from the University of Illinois (arxiv.org/abs/2007.00764) documents Lightning privacy limitations in detail.
Best practices for Lightning privacy include: using private (non-announced) channels; routing through multiple hops; and running a full Lightning node over Tor rather than using a custodial Lightning wallet. The Phoenix wallet (phoenix.acinq.co) and Zeus wallet (zeusln.app) support Tor integration and non-custodial Lightning operation.
How Does Bitcoin Privacy Compare to Privacy Coins?
Academic consensus consistently rates Bitcoin with CoinJoin as providing substantially weaker privacy than Monero or ZCash shielded transactions. The fundamental difference is mandatory versus optional privacy: Monero's ring signatures and stealth addresses operate on every transaction without user action, maintaining a large anonymity set. Bitcoin CoinJoin requires active participation, leaves detectable on-chain signatures, and is vulnerable to post-mix tracing through address reuse and change output analysis.
For users who must use Bitcoin due to platform constraints, the documented best practice is: acquire through a no-KYC peer-to-peer platform; use Wasabi or Sparrow for CoinJoin before spending; operate entirely over Tor; never reuse addresses; and maintain strict UTXO discipline to prevent unintended output linkage. The OPSEC guide covers complementary practices for minimising network-level metadata exposure.