The Privacy Risk of Running a Clearnet Bitcoin Node
Operating a full Bitcoin Core node validates blocks independently, ensuring you never trust third-party servers. However, running a node on a standard clearnet home connection exposes your residential IP address on the global peer list (getpeerinfo), allowing analytics firms to link your physical address to broadcasted transactions.
Configuring Tor v3 Hidden Service in bitcoin.conf
By enabling native Tor support in Bitcoin Core, your node generates a private .onion address and transmits all block and mempool data through encrypted Tor circuits:
# Enable Tor SOCKS5 Proxy proxy=127.0.0.1:9050 listen=1 bind=127.0.0.1 # Enable Tor v3 Hidden Service Creation onion=127.0.0.1:9050 torcontrol=127.0.0.1:9051 torpassword=your_secure_password # Only connect to Tor peers for maximum privacy onlynet=onion
The Benefits of Tor-Only Bitcoin Broadcasting
- Zero IP Leakage: Peers receiving your transactions only see a cryptographic 56-character
.onionaddress. - Immunity to ISP Traffic Throttling: Your ISP cannot inspect Bitcoin protocol traffic or identify node operation.
- Bypass NAT & Port Forwarding: Tor onion routing functions seamlessly behind residential Carrier-Grade NAT (CGNAT) without opening port 8333 on your home router.
Explore our related guide on Lightning Network node IP privacy.
Verify that your Web3 network does not expose residential IP metadata using our free online IP scanner.