I've been thinking about a mistake we make when talking about self-hosting: we often treat physical control of the server as if it automatically meant privacy.
You can run Bitcoin Core at home, verify everything yourself and still expose your residential IP through port forwarding, DNS, Docker networking or other services running beside the node.
So I put together a practical architecture I've been working through:
Internet → disposable VPS → WireGuard → home server
The VPS is only the public edge. No wallet seed, no Bitcoin RPC, no Lightning secrets. Bitcoin Core stays home and can use Tor. Administrative services stay private. If the VPS disappears, the goal is that you replace it rather than lose anything important.
I also went into some easy-to-miss problems: Docker published ports vs UFW, Bitcoin Core's current NAT-PMP behavior, historical DNS leaks, what the VPS/ISP can still observe, and why a WireGuard tunnel should not automatically have access to your entire LAN.
Full guide:
https://davidebtc186.substack.com/p/your-bitcoin-node-is-self-hosted
I'm curious how people here handle this. If you run Core at home, do you use Tor only, direct clearnet, or some kind of remote ingress?
[link] [comments]
You can get bonuses upto $100 FREE BONUS when you:
💰 Install these recommended apps:
💲 SocialGood - 100% Crypto Back on Everyday Shopping
💲 xPortal - The DeFi For The Next Billion
💲 CryptoTab Browser - Lightweight, fast, and ready to mine!
💰 Register on these recommended exchanges:
🟡 Binance🟡 Bitfinex🟡 Bitmart🟡 Bittrex🟡 Bitget
🟡 CoinEx🟡 Crypto.com🟡 Gate.io🟡 Huobi🟡 Kucoin.
Comments