Tor for Cryptocurrency Privacy - Protecting Financial Anonymity

When a Bitcoin wallet broadcasts a transaction to the Bitcoin network, it connects to peer nodes and propagates the transaction. The first node that receives a transaction can often infer that it came from the broadcaster's IP address with reasonable confidence, especially if the wallet connects to few peers. This IP-to-transaction linkage is separate from on-chain analysis and cannot be resolved by on-chain privacy techniques like CoinJoin alone.

Exchanges, blockchain explorers, and blockchain API services collect IP addresses of users who query transaction data. A user who visits a blockchain explorer to check their transaction status from their home IP creates a durable IP-to-address linkage in the explorer's logs. This linkage can be requested by law enforcement or obtained through data breaches.

Tor prevents both types of linkage. Transactions broadcast through Tor appear to the Bitcoin network as originating from a Tor exit node. Blockchain explorer queries made through Tor appear to the explorer as coming from a Tor exit node. Neither provides useful information for linking to the user's real IP address.

Bitcoin Core has native Tor support. Configure in bitcoin.conf:

proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
onlynet=onion

The onlynet=onion setting routes all peer connections through Tor, ensuring no clearnet connections leak the node's real IP. Bitcoin Core will create a .onion address for the node automatically if tor's control port is accessible. Other Bitcoin nodes can connect to your node's onion address, providing a fully anonymous node participation.

For wallets that do not have native Tor support, use torsocks to route all network calls through Tor: torsocks bitcoin-wallet-binary --whatever-options. The torsocks wrapper transparently routes TCP connections through Tor for processes that do not have native proxy support.

Running a full node (storing the complete blockchain) on an anonymous offshore VPS rather than at home removes home IP address exposure entirely. The VPS is accessed through Tor for management; the Bitcoin node's transactions and connections originate from the VPS's IP. For users who run Bitcoin nodes primarily for their own wallet service, this architecture provides the cleanest IP isolation.

Monero provides on-chain transaction privacy (ring signatures, stealth addresses, RingCT) that Bitcoin lacks. Combined with Tor for the network layer, Monero transactions provide both on-chain unlinkability and IP anonymization. This combination is significantly stronger than either measure alone.

Monero's GUI wallet includes built-in Tor support. Enable it in Settings > Interface > Tor/I2P anonymity network. The wallet routes all network connections through Tor automatically. The Monero daemon (monerod) also supports --proxy and --anonymous-inbound flags for Tor integration on VPS deployments.

For maximum privacy in Monero transactions: generate receiving addresses on an air-gapped device, broadcast transactions from a Tor-connected device, and use subaddresses (single-use receiving addresses) to prevent linking multiple received transactions to the same wallet. Monero's Dandelion++ protocol provides additional transaction propagation privacy by delaying rebroadcast to prevent IP-to-transaction correlation even within the Monero network.