Tor (The Onion Router)

Tor (The Onion Router) is a free, open-source anonymity network that conceals who is talking to whom by routing each connection through a chain of three volunteer-operated relays. The client wraps the data in nested layers of encryption — one per relay — so that each hop peels away a single layer, like the skins of an onion, before passing the traffic on. This is why the technique is called onion routing.

The three-relay circuit

A standard Tor circuit uses a guard (entry) relay, a middle relay, and an exit relay. The guard sees the user's real IP address but not the final destination; the exit sees the destination but not the user's IP; the middle relay sees neither endpoint, only the two relays on either side of it. Because no single relay holds both ends of the conversation, an observer must compromise or watch multiple points simultaneously to deanonymize a user — a deliberately high bar that resists casual traffic analysis.

Why it matters for sovereign Bitcoiners

For self-hosters, Tor is a practical building block. A Bitcoin full node can advertise and accept connections over Tor so that the node's home IP address is never exposed to peers, and wallets can broadcast transactions through Tor to break the link between a payment and a residential network. The trade-off is latency: layered encryption and three hops make Tor noticeably slower than a direct connection, and exit relays can see unencrypted traffic, so end-to-end encryption (HTTPS, or an onion service) still matters.

Tor pairs naturally with related tools in this glossary. See Onion Service (.onion) for connections that never leave the Tor network, I2P for an alternative anonymity layer, and Threat Model for deciding when Tor actually fits your risk profile.

Onion Services: Self-Hosting Without an Open Port

Beyond anonymous browsing, Tor solves a mundane self-hosting problem: reachability. An onion service builds its circuits outward to rendezvous points inside the Tor network, so a node or dashboard on your LAN becomes reachable from anywhere without port forwarding, a public IP, or a hole in your firewall — and without ever advertising your home address. Traffic to a .onion address also never exits the network, so there is no exit relay to observe it, and the onion address itself authenticates the service cryptographically. For a home Bitcoin node, this means peers and your own remote wallet can reach you while your residential IP stays out of every peer list on the network.

Limits and the Honest Threat Model

Tor's design resists any single observer, not every observer. A global adversary that can watch both your guard connection and the destination can correlate timing and volume; this is outside Tor's threat model by explicit design. Exit relays can read and tamper with plaintext, so anything leaving through an exit still needs end-to-end encryption. Latency is real — three hops and layered crypto make interactive use noticeably slower — and high-volume transfers degrade the network for everyone. The sober summary: Tor raises the cost of surveillance dramatically, and pretending it does more than that is how operators get burned.

Practical Notes for a Node Operator

Bitcoin Core has first-class Tor support: it can create its own onion service through the Tor control port, connect out through the SOCKS proxy, and be restricted to onion-only peers for maximum address privacy. The trade-offs are slower initial block download and dependence on the local Tor daemon staying healthy. Many operators run dual-stack — clearnet plus onion — to keep good peer diversity while still offering a private path in. Treat the Tor daemon like any other critical service in your self-hosting stack: keep it updated, monitor it, and know what breaks when it stops.