Running your Bitcoin node over Tor hides your IP address from peers and your ISP. Here's how to configure Tor for Bitcoin Core, Umbrel, Start9, and RaspiBlitz in 2026.
Running a Bitcoin node already improves your privacy by validating transactions without trusting third parties. But your node's IP address — visible to peers it connects to — can be linked to your Bitcoin activity. Running your node over Tor hides your IP address from peers, significantly improving network-level privacy.
Here's how to configure Tor for your Bitcoin node in 2026.
When your Bitcoin node connects to peers, those peers see your IP address. With enough peer connections or transaction timing analysis, a sophisticated observer could potentially link your IP address to your Bitcoin transactions — even if you use a different Bitcoin address for each transaction.
Specific risks:
ISP visibility: Your internet service provider can see you're running a Bitcoin node. In most jurisdictions this is legal, but it's information you may not want to share.
Peer surveillance: Malicious peers (run by chain analysis firms, governments) might log connection metadata. Over time, connection patterns can reveal transaction origins.
Geolocation: Your IP address reveals your approximate geographic location.
Tor addresses all three by routing your node's network traffic through an encrypted circuit of three volunteer relays.
Tor protects:
Tor does NOT protect:
For complete Bitcoin privacy, Tor is one layer — combine with Taproot addresses, avoid UTXO consolidation, and consider CoinJoin for on-chain privacy.
Each major node software package has different Tor integration:
Install Tor on your system:
sudo apt install torbrew install torStart Tor: tor & (runs as a background service)
Configure bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
onlynet=onion
HiddenServiceDir /var/lib/tor/bitcoin/
HiddenServicePort 8333 127.0.0.1:8333
bitcoin-cli getpeerinfo | grep addr
Umbrel makes Tor configuration nearly automatic:
This is the easiest path — Umbrel handles all the technical configuration.
Start9 Embassy routes all services through Tor by default. Bitcoin node runs on Tor automatically — no additional configuration needed. Start9 provides your node's .onion address for wallet connections.
RaspiBlitz has built-in Tor configuration as part of its setup wizard. Select Tor routing during initial setup or enable it later via the config menu.
myNode includes Tor support in its dashboard. Enable it under the Bitcoin settings section.
Once your node is running over Tor, connect your wallet to it for complete privacy:
Sparrow Wallet: In Preferences → Server, enter your node's .onion address. Sparrow supports Tor natively (uses built-in Tor client).
BlueWallet: In Lightning settings (or Bitcoin node settings), enter your node's .onion address. Requires BlueWallet Tor to be enabled.
Electrum: In Server preferences, enter your Electrum server's .onion address if you're running an Electrum server alongside your Bitcoin node.
Zeus: In node connection settings, enter your LND or Core Lightning node's .onion address for Lightning connections.
Tor adds latency. Expect:
Recommendation: During initial block download (IBD), use clearnet mode (onlynet=all or no restriction) to download the blockchain faster. After syncing, switch to Tor-only mode.
Some users run hybrid mode: connecting to both Tor and clearnet peers, with their own traffic going through Tor. This balances privacy with performance.
When you create a Tor hidden service for your node, Bitcoin Core generates a .onion address. This is your node's private address on the Tor network.
Benefits:
Problem: No Tor peers connecting
Check Tor is running: systemctl status tor
Verify proxy settings in bitcoin.conf: proxy=127.0.0.1:9050
Check Bitcoin Core logs: debug.log should show Tor-related connection attempts
Problem: Slow sync speed
Normal — Tor is slower. If too slow, allow clearnet connections during sync: remove onlynet=onion
Problem: Cannot reach local wallet through Tor
Verify your .onion address is correct. Check that the Tor hidden service is active. Some wallets require Tor browser-level configuration to reach .onion addresses.
Yes. Tor adds latency and reduces throughput. For initial sync (IBD), using clearnet is much faster. For ongoing operation, the privacy benefit outweighs the performance cost for most users.
Yes, in virtually all jurisdictions. Running a Bitcoin node is legal (it's just software that validates the blockchain). Tor usage is legal in most countries, though some authoritarian jurisdictions restrict it.
Yes. If you run a Lightning node alongside your Bitcoin node, you can configure Lightning (LND, Core Lightning) to run over Tor as well. Umbrel and Start9 handle this automatically alongside Tor-enabled Bitcoin Core.
No. Tor hidden services work regardless of your IP address, making them excellent for home users with dynamic IP addresses from their ISP.
Explore node options in our Bitcoin Node Directory. See also: How to Run a Bitcoin Node and Bitcoin Node Privacy Benefits.
Get our free Beginners Guide to Buying Bitcoin plus weekly insights for long-term holders.
A Bitcoin full node downloads 600+ GB during initial sync and uses 200+ GB/month ongoing. This guide covers exact bandwidth requirements by connection type, how to manage upload costs, and whether pruning helps.
Running your own Bitcoin node protects your financial privacy in ways most users never consider. This guide explains exactly what threats a personal node defends against and how to set it up correctly.
How much bandwidth does a Bitcoin node use? Complete breakdown of IBD data, ongoing monthly usage, pruned vs full node differences, and how to limit bandwidth.