TL;DR
For an anonymous Bitcoin or Lightning node in 2026:
- Storage: Bitcoin full node ≈ 600+ GB pruned, 1+ TB unpruned. Pick a VPS with NVMe storage and good IOPS.
- Bandwidth: budget 200–500 GB/month outbound for a healthy node. Pick unmetered or generously-metered plans.
- Provider: Privex (crypto-only signup), FlokiNET (Monero + cash), BuyVM Luxembourg (best $/GB for storage).
- Network: run over Tor (
bitcoind -onion); listen on.onionfor inbound peers. - Identity: no real name in signup, no real-name SSH keys, payment in XMR.
Why offshore + anonymous matters
A Bitcoin node by itself is not illegal anywhere reasonable, but several adjacent activities have higher friction:
- Lightning routing nodes that handle high payment volume can attract money-services-business questions in some jurisdictions.
- Custom Bitcoin software (alternative implementations, fork experiments, mempool research) sometimes attracts copyright-style takedowns when you publish modified code.
- Public node operation with a stable identity is, by definition, public. If you don’t want the on-chain analytics community to map your node to your real identity, anonymous infrastructure is required.
For node operators who’d rather not have their real-name email associated with their node’s IP for the next decade, offshore + anonymous + crypto-paid hosting is the default.
Storage and bandwidth requirements (May 2026)
| Component | Disk | Bandwidth (out) |
|---|---|---|
bitcoind pruned (550 MB) | ~5 GB | 50–100 GB / month |
bitcoind pruned (default) | ~50 GB | 100–300 GB / month |
bitcoind full archival | ~700 GB+ | 200–500+ GB / month |
| Electrum server (electrs) | +200 GB | minimal |
| Lightning node (LND/CLN) | +5 GB | 10–50 GB / month |
| Lightning routing node (busy) | +20 GB | 100+ GB / month |
Storage is the binding constraint. A 1 TB NVMe VPS is the minimum for an unpruned node + electrs.
Step-by-step
1. Pick the VPS
For storage-heavy workloads, look at:
- BuyVM Luxembourg — pair the entry KVM Slice with a Block Storage Slab volume. Cheapest $/GB on the directory.
- Privex — crypto-only signup, multiple Nordic DCs, good for fully-anonymous deployments.
- FlokiNET — pricier per spec but Monero + cash payment + multi-jurisdiction.
- HostHatch — has dedicated “storage VPS” tiers that fit Bitcoin archival nodes well.
Avoid US-only datacenters if your node will publicly route Lightning payments at scale.
2. Acquire it anonymously
Follow the anonymous Monero VPS guide. Pay in XMR, sign up over Tor, throwaway email.
3. Install Bitcoin Core over Tor
# Install bitcoind from official binaries verified against gpg signatures
# Then in bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
discover=0
onlynet=onion
externalip=YOUR_ONION.onion
Pair with tor running locally and a HiddenServicePort 8333 127.0.0.1:8333 for inbound peers.
4. Optional: Electrum server
If you want a personal Electrum backend (no third-party query leakage):
# electrs configuration
network = "bitcoin"
db_dir = "/var/lib/electrs"
daemon_dir = "/var/lib/bitcoind"
electrum_rpc_addr = "127.0.0.1:50001"
Expose via Tor onion — never on clearnet.
5. Optional: Lightning node
LND, Core Lightning (CLN) and Eclair all support Tor. For a private node:
# in lnd.conf
[Tor]
tor.active=true
tor.v3=true
tor.streamisolation=true
tor.skip-proxy-for-clearnet-targets=false
listen=localhost
externalip=YOUR_LND_ONION.onion
For a routing node, this is fine but routing performance is lower over Tor than clearnet. Trade-off your priorities.
6. Backup wallet keys
Critical: back up the wallet seed offline. The VPS can be lost (provider issue, court order, hardware failure) and you must be able to reconstruct from seed. Print it on paper or store on hardware (Cryptosteel, hardware wallet).
Operational pitfalls
- Pruning later: deleting blocks after running unpruned is not trivial. Decide pruned vs full before initial sync.
- Fee sniping at startup: a fresh node has no peers; bootstrap from
addnodewith known-good Tor peers. - Wallet on the VPS: don’t keep large balances on the same machine that’s publicly visible. Use a watch-only wallet on the node and keep keys offline.
- Lightning channel state: losing channel state can lose your money. SCB (static channel backup) or watchtower on a separate machine is mandatory for non-trivial channels.