Home / Servers / Bitcoin Node VPS

Run a Bitcoin full node on a VPS

A pruned bitcoind validates every block from genesis and keeps only 550 MiB of recent block files plus the chainstate, about 15 GB by Bitcoin Core's own estimate, so it fits Blackbox Core with room to spare. If the node holds a wallet, Blackbox encrypts the memory its key sits in. Sign up with a generated credential and pay in bitcoin.

Deploy a node VPS from $9.99 a monthenough for a pruned node
  • Bitcoin Core 32.1
  • Tor-only bitcoind
  • Pay in BTC or XMR
  • No email or ID

Which node fits which plan

Pruning decides how much disk the node needs. Decide on it before you pick a plan.

Disk it needsPlan that fits
Pruned, prune=550 550 MiB of blocks plus the chainstate, which Bitcoin Core budgets at 14 GB Blackbox Core: 50 GB, $9.99 a month. Every larger plan has room too.
Pruned, prune=100000 About 100 GB of recent blocks, enough to serve peers and rescan a wallet months back Blackbox Max: 200 GB, $39.99 a month, or a standard VDS-350 (160 GB) and up
Archival About 756 GB in July 2026 (Bitcoin Core 32.1 budgets 897 GB), growing about 82 GB a year None. The largest disk here is 400 GB.
Archival plus electrs Over 850 GB None. Run electrs on signet, or point your wallet at a pruned Core over SSH.

Chain sizes: Bitcoin Core 32.1 and Coin Bureau, July 2026. electrs figures: its usage guide.

What else the node needs

Disk is the hard limit. RAM, disk speed and traffic are easy to meet from Blackbox Core up.

RAM
bitcoin.org asks for 2 GB. Since 31.0, Bitcoin Core defaults dbcache to 1024 MiB when it detects at least 4096 MiB of RAM, and a smaller cache makes the first sync much slower. A 4 GB VM can report a little under that, so the quick start sets dbcache=1024 itself. Blackbox Nano has 2 GB, which is bitcoin.org's minimum, so this page starts at Core with 4 GB.
Disk speed
At least 100 MB/s, per bitcoin.org. Every plan here is on NVMe.
First sync
Anywhere from about 12 hours to several days, depending on hardware, dbcache and peers. With a matching UTXO snapshot, loadtxoutset (on mainnet since Core 28.0) gives a usable node in minutes.
Traffic
About 740 GB down for the first sync, then around 20 GB down a month, per bitcoin.org, which adds that nodes on fast connections often upload 200 GB or more a month. Blackbox Core includes 4 TB per 31 days. Standard plans are unmetered.
Ports
Clearnet peers connect on 8333. A Tor-only node needs no open port: the onion service reaches bitcoind on 127.0.0.1:8334. Keep the RPC (8332) on localhost.

Quick start: a pruned, Tor-only bitcoind on Debian 13

Bitcoin Core 32.1, verified, under systemd. Run it as root on a fresh 4 GB server. Each step links its source.

# 1. Dependencies, including the Tor daemon the node will speak through.
apt update && apt install -y wget gnupg git tor

# 2. Fetch the release, the checksums, and the signatures on the checksums.
#    https://bitcoincore.org/en/download/
cd /tmp
wget https://bitcoincore.org/bin/bitcoin-core-32.1/bitcoin-32.1-x86_64-linux-gnu.tar.gz
wget https://bitcoincore.org/bin/bitcoin-core-32.1/SHA256SUMS
wget https://bitcoincore.org/bin/bitcoin-core-32.1/SHA256SUMS.asc

# 3. Hash first, then the signatures over the hash file. Builder keys live at
#    builder-keys/<signer>.gpg: https://github.com/bitcoin-core/guix.sigs
sha256sum --ignore-missing --check SHA256SUMS
git clone https://github.com/bitcoin-core/guix.sigs
gpg --import guix.sigs/builder-keys/*.gpg
gpg --verify SHA256SUMS.asc SHA256SUMS   # want lines reading "gpg: Good signature"

# 4. Install. Bitcoin Core's systemd unit calls /usr/bin/bitcoind.
tar xzf bitcoin-32.1-x86_64-linux-gnu.tar.gz
install -m 0755 -o root -g root -t /usr/bin bitcoin-32.1/bin/*

# 5. Let Bitcoin Core create its own onion service through the Tor control
#    port. https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md
cat >> /etc/tor/torrc <<'TORRC'
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1
DataDirectoryGroupReadable 1
TORRC
adduser --system --group --home /var/lib/bitcoind bitcoin
usermod -a -G debian-tor bitcoin     # so bitcoind can read Tor's auth cookie
systemctl restart tor

# 6. Config: pruned, and reachable over onion only.
mkdir -p /etc/bitcoin
cat > /etc/bitcoin/bitcoin.conf <<'CONF'
# MiB of raw block and undo data to keep. 550 is the minimum allowed and fits
# Blackbox Core (50 GB disk). 100000 keeps about 100 GB of recent blocks and
# wants Blackbox Max (200 GB) or larger. Pruning is incompatible with -txindex.
prune=550
# Since 31.0 the default is 1024 MiB only where at least 4096 MiB of RAM is
# detected. A 4 GB VM can report slightly less, so set it here.
dbcache=1024
# Outbound through the local Tor SOCKS proxy, onion peers only.
proxy=127.0.0.1:9050
onlynet=onion
# listen defaults to off behind a proxy; bind the inbound side to loopback
# so the onion service is the only way in.
listen=1
bind=127.0.0.1:8334=onion
# Target for outbound traffic per 24h in MiB; historic blocks are cut first.
# 144 MiB/day is the recommended minimum: https://bitcoin.org/en/full-node
maxuploadtarget=5000
CONF
chown root:bitcoin /etc/bitcoin/bitcoin.conf && chmod 640 /etc/bitcoin/bitcoin.conf

# 7. Bitcoin Core's systemd unit. It runs as the bitcoin user and creates
#    /etc/bitcoin, /var/lib/bitcoind and /run/bitcoind itself. Locally
#    installed units go in /etc/systemd/system; /lib/systemd/system belongs
#    to packages and gets overwritten.
#    https://github.com/bitcoin/bitcoin/blob/v32.1/contrib/init/bitcoind.service
wget -O /etc/systemd/system/bitcoind.service \
  https://raw.githubusercontent.com/bitcoin/bitcoin/v32.1/contrib/init/bitcoind.service
systemctl daemon-reload && systemctl enable --now bitcoind

# 8. Watch it sync. verificationprogress runs 0 to 1, and
#    initialblockdownload flips to false once the node is caught up.
bitcoin-cli -datadir=/var/lib/bitcoind getblockchaininfo

# 9. Check the isolation: only onion should be reachable, and
#    localaddresses should hold one .onion address.
bitcoin-cli -datadir=/var/lib/bitcoind getnetworkinfo

# 10. Reach the RPC from your own machine over SSH, never over the internet.
#     This config sets no rpcauth, so the only credential is the .cookie file
#     bitcoind writes into /var/lib/bitcoind, with a new random password on
#     every start. For a remote wallet, add an rpcauth= line to bitcoin.conf
#     (share/rpcauth/rpcauth.py in the release tarball makes one) and give
#     the wallet that user and password. Run this locally, then point Sparrow
#     or Specter at 127.0.0.1:8332:
#     ssh -N -L 8332:127.0.0.1:8332 root@YOUR_SERVER_IP

Keep a wallet on Blackbox

An unlocked Bitcoin Core wallet keeps its decryption key in RAM until the walletpassphrase timeout runs out. On an ordinary VPS the host can read that memory. On a Blackbox the CPU encrypts it, and the host sees ciphertext.

MontrealAmsterdamNew York City (launch pre-order)
Deploy Blackbox from $9.99 a month
  • AMD SEV-SNP encrypts guest memory on Linux images, with debug disabled in the launch policy and /dev/sev-guest available for attestation.
  • No guest agent and no virtio-serial port, so the panel has no way into a running VM and cannot reset the root password.
  • LUKS2 disk encryption under a passphrase you set on your first SSH login. Servury never holds it, so losing it loses the data.
  • Measured boot you can check with blackbox-verify before you type that passphrase.
  • A 10 Gbps port with 2 to 32 TB of transfer per 31 days, then 10 Mbps until the period rolls over. IPv4 plus a routed IPv6 /64.

How Blackbox works

Blackbox plans

Each of these runs a pruned node. Pick a bigger disk for a wider prune window.

PlanvCPURAMNVMeTrafficWherePrice
Blackbox Core 2 4 GB 50 GB 4 TB per 31 days MontrealAmsterdamNew York City (launch pre-order) $9.99/mo
Blackbox Plus 4 8 GB 100 GB 8 TB per 31 days MontrealAmsterdamNew York City (launch pre-order) $19.99/mo
Blackbox Max 6 16 GB 200 GB 16 TB per 31 days MontrealAmsterdamNew York City (launch pre-order) $39.99/mo
Blackbox Ultra 8 32 GB 400 GB 32 TB per 31 days MontrealAmsterdamNew York City (launch pre-order) $79.99/mo
Any term from 7 to 365 days, prorated by the day. Blackbox: AMD SEV-SNP encrypted memory on Linux images, a dedicated IPv4, a routed IPv6 /64 and a 10 Gbps port. Past the transfer allowance the port drops to 10 Mbps until the period rolls over; nothing extra is billed. Pre-orders are paid now, deploy when room opens, and are final. Deploy

Standard VPS and VDS plans in New York City, Singapore and Hong Kong run a pruned node too, with unmetered bandwidth and IPv4 only. They have no memory encryption.

How much server a Bitcoin node needs

A Bitcoin node VPS is a rented server running bitcoind, so your wallet checks its own transactions instead of asking someone else's server for its balance. On a VPS, prune it: a pruned node still validates every block and every signature from genesis and keeps the whole UTXO set. It deletes only raw block files it has already checked, and those take most of the disk.

Disk

Core's help text says prune=N prunes old blocks "if a target size in MiB is provided" (init.cpp), and "The minimum allowed is 550MB", enough for about 288 blocks or two days (Bitcoin Core 0.11.0 release notes). bitcoin.org says pruning takes disk usage "from over 750GB to around 7GB" (Running A Full Node), but Bitcoin Core's own estimate is higher now: version 32.1 budgets 14 GB of free space for a pruned node's chainstate, not counting the prune target (chainparams.cpp). Coin Bureau's July 2026 figure for an archival node is "approximately 756GB", growing "roughly 82GB" a year (Coin Bureau). Bitcoin Core 32.1 itself budgets 897 GB for an archival node's data directory (chainparams.cpp).

Memory, sync time and bandwidth

bitcoin.org asks for 2 GB of RAM and a disk that reads at least 100 MB/s. Bitcoin Core 31.0 raised the default -dbcache to "1024 MiB from 450 MiB on systems where at least 4096 MiB of RAM is detected" (31.0 release notes), and a lower dbcache "makes initial sync time much longer" (reduce-memory.md), which makes 4 GB the sensible floor. A 4 GB VM can report slightly less than 4096 MiB, so the quick start sets dbcache=1024 by hand. bitcoin.org puts the first sync at "at least several days". Jameson Lopp's 2025 tests took Core 30.0 to block 928,000 in "12 hours 7 minutes" with dbcache=24000 and a local peer (2025 node performance tests). Core 26.0 added loadtxoutset, which gives "a usable bitcoind instance that is current with the network tip in a matter of minutes rather than hours" while the original chainstate validates behind it (26.0 release notes). On mainnet it needs Core 28.0 or later, which added mainnet parameters for a snapshot at height 840,000 (28.0 release notes). After the roughly 740 GB first sync, bitcoin.org expects "around 20 gigabytes" a month down and says nodes on fast connections commonly use "200 gigabytes upload or more a month".

Electrs and wallets

The Electrum server most people want needs an unpruned node. Its usage guide starts bitcoind with -prune=0, says the index "should be ~7% of the blocks/*.dat files, but it may increase to ~14% at the end of the initial sync", and shows "56G" for its own reference run (electrs usage guide). Its example config asks for "at least 70GB of free space" for the index directory (electrs config_example.toml). Together that is roughly 860 GB by Coin Bureau's figure, and more by Bitcoin Core's own estimate. A pruned node with your wallet talking straight to Core through an SSH tunnel does fit. Sparrow says "Running a pruned node is fine", with rescans limited to the blocks you kept (Sparrow docs).

Wallet keys and the host

walletpassphrase "Stores the wallet decryption key in memory" for the timeout you give it (Core RPC docs), and on an ordinary VPS the host can read that memory. Blackbox encrypts guest RAM with AMD SEV-SNP, has no guest agent, and encrypts the disk with LUKS2 under a passphrase only you know (SEV-SNP VPS). Cryptocurrency mining is prohibited by the terms, and a node is not mining. A Tor-only node is also different from a Tor relay, because it carries only its own traffic. To pay for the server in BTC, see the Bitcoin VPS page.

Logs and uptime

The site keeps no access logs and runs no analytics or third-party scripts on public pages (privacy policy). The warrant canary is PGP-signed, the status page shows live uptime for each node, and the terms commit to 99.9% availability.

Start a pruned node

Blackbox Core runs bitcoind with prune=550. Sign up with a generated credential and pay in bitcoin, Monero, another coin, by card or with cash by mail.

Deploy a node VPS from $9.99 a month

Questions

How much disk does a Bitcoin node need on a VPS?

Very little if you prune it. At prune=550, the minimum, the node keeps 550 MiB of recent block files plus the chainstate, and Bitcoin Core 32.1 budgets 14 GB of free space for that chainstate. bitcoin.org still quotes an older figure of around 7 GB. An archival node was about 756 GB in July 2026 and grows by roughly 82 GB a year. Bitcoin Core 32.1 itself budgets 897 GB for an archival node's data directory. The largest disk on any plan here is 400 GB, so a pruned node fits and an archival node does not.

What does a pruned node give up?

History. A pruned node still validates every block and every signature and keeps the full UTXO set. It cannot serve old blocks to peers, cannot rescan a wallet past the oldest block it kept, and cannot run -txindex, which Bitcoin Core refuses to combine with pruning.

Can I run electrs on a Servury VPS?

Not on mainnet. The electrs usage guide starts bitcoind with -prune=0, and the index adds roughly 7 to 14 percent on top of the block files (56 GB in the project's own reference run). That comes to roughly 860 GB by Coin Bureau's figure and more by Bitcoin Core's own estimate, and the largest disk here is 400 GB. On signet or testnet it fits easily.

How long does the initial block download take?

It varies a lot. bitcoin.org still says at least several days on modest hardware. Jameson Lopp's 2025 test synced Bitcoin Core 30.0 to block 928,000 in 12 hours and 7 minutes on a 6-core desktop with dbcache=24000 and a local peer. Core 26.0 added loadtxoutset, which loads a UTXO snapshot and brings a node level with the network tip in minutes while the original chainstate validates behind it. Mainnet snapshots work from Core 28.0.

Can the node talk only over Tor?

Yes. Bitcoin Core documents the settings: proxy=127.0.0.1:9050 for outbound connections, onlynet=onion to keep them on .onion peers, listen=1 because listening is off by default behind a proxy, and bind=127.0.0.1:8334=onion for inbound. With tor running ControlPort 9051 and cookie authentication, Core creates its own onion service.

Is it safe to keep a wallet on a hosted node?

That depends on the host. The walletpassphrase RPC keeps the wallet decryption key in memory for the timeout you set, and on ordinary virtualisation the host can read guest RAM. On Blackbox the CPU encrypts guest memory with AMD SEV-SNP and there is no guest agent in the VM. Keep large balances on hardware you hold.

Can I mine on the same server?

No. The terms prohibit cryptocurrency mining of any kind, and it leads to suspension. A node, a wallet or a signing service is fine.

Guides on this topic

Related pages

Support

Questions before you buy? Ask here. You do not need an account: your first message creates one, and you get its credential to come back for our reply.