VPS-PRO · VPS
- AMD EPYC 9124 (16 vCPU)
- 64 GB DDR5 · 1 TB NVMe
- 2 Gbps · Unlimited bandwidth
1 TB NVMe runs a full node today with modest headroom, or a pruned node forever. The cheapest way to own your validation.
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.
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.
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.
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 tor
Download 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 Tor
Watch 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.
Related reading: VPS vs Dedicated Server for Privacy-Critical Workloads · The First Hour of VPS Hardening: A Checklist · Crypto nodes