Run Bitcoin Core on hardware that matches the chain: NVMe for a fast initial block download, unlimited bandwidth for 24/7 relaying, and an offshore IP that keeps your home address out of the peer list. Paid in BTC, deployed with a token.
A full node is the only way to use Bitcoin without trusting someone else's server: it validates every block against consensus rules, broadcasts your transactions without a middleman, and strengthens the network's censorship resistance. The blockchain passed roughly 760 GB in 2026 and grows ~100 GB a year — a Raspberry Pi at home struggles, and a home IP broadcasts who you are. A rented offshore server with NVMe and unmetered traffic solves both problems at once.
Initial block download is disk-bound: on NVMe with dbcache=8000, mainnet syncs in 6–24 hours instead of weeks on spinning rust.
A well-connected node moves 1–3 TB a month with 125 connections. Unlimited bandwidth means you never have to cap maxuploadtarget.
Point Sparrow, Electrum or Bitcoin Core's own wallet at your node over SSH or Tor and every payment you receive is verified by machinery you control.
One config line runs P2P over Tor: your node's real location stays private, and hidden-service peers connect inbound with no port-forward drama.
Realistic sizing for a mainnet node in 2026 — chain size, memory, disk and bandwidth. Based on what actually runs in production, not on minimum specs that stopped being true two years ago.
| Client software | Bitcoin Core 29.x |
|---|---|
| Chain size | ≈ 760 GB |
| Growth per year | ≈ 100 GB / year |
| Recommended RAM | 8–16 GB |
| Recommended storage | 2 TB NVMe |
| Initial sync | 6–24 h |
| Prunable | ✓ (to ~50 GB) |
| P2P port | 8333 TCP |
Every plan ships with unlimited bandwidth, NVMe storage and full root access — the three things a node actually consumes. Deploy with a token, pay in the same coin your node secures.
1 TB NVMe runs a full node today with modest headroom, or a pruned node forever. The cheapest way to own your validation.
The sweet spot: 2× 1 TB NVMe (chain on one, OS and headroom on the other), 64 GB ECC RAM for a huge dbcache, 8 cores for parallel script validation.
txindex=1, electrs or Fulcrum for your own Electrum server, Lightning on the side — 2× 2 TB NVMe and 16 modern cores absorb it all.
| Location | CPU | RAM | Storage | Uplink | Price | |
|---|---|---|---|---|---|---|
| Moldova Budget Offshore | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $48.50/mo | Order |
| Russia Western-Proof | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $48.50/mo | Order |
| Panama No Data Retention | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $53.50/mo | Order |
| Romania Anti-Retention | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $53.50/mo | Order |
| Netherlands Best Peering | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $58.50/mo | Order |
| Iceland Free Speech Haven | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $63.00/mo | Order |
| Switzerland Premium Privacy | 8C / 16T Intel Xeon E-2388G (3.2 GHz) |
64 GB DDR4 ECC | 2x 1TB NVMe | 2 Gbps | $68.00/mo | Order |
Need more disk, RAM or a custom RAID layout for your node? Contact →
From order to synced node. Commands are copy-paste ready for Ubuntu 24.04 — adapt paths if you run Debian or Rocky.
Pick DS-1 (or VPS-PRO for pruned) in the jurisdiction you prefer — Netherlands for peering, Switzerland for maximum legal protection. Pay in BTC, get root in minutes.
Key-only SSH, firewall allowing 22 and 8333, unattended security upgrades — then install Tor so the node can broadcast privately.
apt update && apt install -y tor
systemctl enable --now torDownload the release, verify the signatures against the guix attestations, install the binaries.
wget https://bitcoincore.org/bin/bitcoin-core-29.0/bitcoin-29.0-x86_64-linux-gnu.tar.gz
tar xzf bitcoin-29.0-x86_64-linux-gnu.tar.gz
install -m 0755 bitcoin-29.0/bin/* /usr/local/bin/server=1, a dbcache as large as your RAM allows, txindex if you'll run Electrum tooling, optional Tor proxy. Start bitcoind and let the initial block download run.
# ~/.bitcoin/bitcoin.conf
server=1
dbcache=8000
txindex=1
proxy=127.0.0.1:9050 # optional: p2p over TorWatch verificationprogress reach 1.0, then point your desktop or mobile wallet at your own RPC over an SSH tunnel or a Tor hidden service.
bitcoind -daemon
bitcoin-cli getblockchaininfo | grep -E 'blocks|verificationprogress'The chain is ~760 GB with default settings and grows roughly 100 GB a year; add ~110 GB if you enable txindex. 8 GB RAM is workable, 16–64 GB turns into real sync speed via dbcache. CPU matters mostly during initial download — 8 modern cores validate signatures faster than the disk feeds them. Budget 2 TB of NVMe and you will not think about disk again before 2032. Pruned mode keeps consensus-full validation in ~50 GB if you don't need to serve historical blocks.
A pruned node validates everything but discards old blocks — perfect for private wallet verification on a smaller VPS. A default full node also serves historical blocks to the network. Add txindex=1 plus electrs or Fulcrum and your node becomes an Electrum server: your hardware wallet gets balance queries answered by your own machine instead of a public server that logs xpubs. The Performance tier exists precisely for that stack, with room for a Lightning node beside it.
Chain-analysis firms crawl the P2P network and map nodes to ISPs and homes. Broadcasting your own transactions from your own IP is a privacy leak that pruning can't fix. An offshore node in a no-logs jurisdiction breaks that link: peers see a datacenter IP in Reykjavík or Zurich, your wallet connects through an encrypted tunnel, and the hosting record behind it is a token paid in BTC — not a name.
Updates are a two-minute affair: stop bitcoind, swap binaries, start, watch the log. Enable unattended OS security updates, keep 20% disk free, and snapshot your bitcoin.conf. If you outgrow the box, order the next tier, rsync the datadir or resync fresh, and release the old server — no ticket, no phone call, no identity. Uptime isn't consensus-critical for a plain full node, but peers remember reliable nodes, and a stable relay earns better connectivity.
A pruned node runs on a VPS from $17/mo. A comfortable full node is the DS-1 dedicated tier at $48.50–68/mo depending on jurisdiction. An archival node with Electrum tooling fits DS-2 from $87.50/mo. All unmetered.
On DS-1 hardware with dbcache=8000 and a 2–10 Gbps uplink: typically 6–24 hours for mainnet. The bottleneck alternates between peer throughput early and script validation later — NVMe keeps both fed.
Yes — install Tor, add proxy=127.0.0.1:9050 and listenonion=1, and Bitcoin Core will build circuits outbound and accept inbound peers over a hidden service. Expect slightly slower sync; many operators sync over clearnet first, then switch.
Running a node is legal in all seven of our jurisdictions — it's equivalent to running any P2P software. It is not mining, not money transmission, and holds no customer funds.
Every server ships a dedicated IPv4 that doesn't change, plus L3/L4 DDoS filtering. For inbound peers just open 8333; behind Tor you don't even need that.
Yes — DS-1 handles bitcoind + LND comfortably; DS-2 adds electrs/Fulcrum headroom. See the dedicated Lightning node page for channel-management specifics.
Ethereum Node Hosting
Monero Node Hosting
Solana Validator & RPC Hosting
Litecoin Node Hosting
TRON Node Hosting
All node types →
Related reading: VPS vs Dedicated Server for Privacy-Critical Workloads · The First Hour of VPS Hardening: A Checklist · Crypto nodes
DS-1 with 2× 1 TB NVMe deploys in minutes. Pay in BTC, sync tonight, verify forever.