Running Bitcoin Core over Tor: Proxy and Privacy Boundaries

This guide explains Bitcoin Core Tor configuration in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.

Outbound proxy routing

The proxy option routes supported network connections through SOCKS5 and can also provide onion reachability. Verify getnetworkinfo and Tor logs for each network type. A working onion connection does not prove every clearnet or name-resolution path uses Tor.

Automatic onion listening

With a compatible Tor control socket, Core 0.12 could create an ephemeral hidden service and advertise the onion address. Listenonion, torcontrol and torpassword governed the feature. Protect control authentication because it can manage Tor state, and record whether identity persists or changes across restart.

Stream isolation

Core had introduced randomised SOCKS credentials to encourage Tor stream isolation. This reduces correlation between destinations but does not erase timing, volume or application-level linkage. Confirm the configured proxy supports the expected authentication behaviour and do not disable isolation casually.

Listening and discovery leaks

Using a proxy changed listening defaults, while explicit listen, bind, externalip and discover settings could expose interfaces or addresses. Inspect effective sockets and advertised addresses over IPv4, IPv6 and onion. Test from outside the host rather than accepting configuration review as proof.

DNS and dependency paths

Name lookups, package updates, NTP, monitoring, RPC clients and pool software may bypass Core’s proxy. Map the whole host and application data flow. Tor for P2P does not automatically protect web APIs, wallet callbacks or the administrator’s browser.

Mining-node trade-offs

Tor adds latency and variable availability. A pool validator needs timely blocks and diverse independent paths. Use Tor as one deliberate connection class rather than the only unmeasured template path, and monitor propagation, peer diversity and failover without publishing private topology.

How specialists test it

Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.

Conclusion

Tor can improve Bitcoin Core network privacy and onion reachability, but only when proxy, control, listener, DNS and application paths are verified together. Treat fallback and clearnet exposure as explicit operational decisions.