No KYC · seven Linux VPS plans, one price in six cities · Pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR
Language: English
Configure a VPS

Guide · Bitcoin · checked 16 November 2026

How do I run a Bitcoin node on a VPS?

Last updated: · 4 min read

Quick answer

How do I run a Bitcoin node on a VPS?

To run a Bitcoin node on a VPS, download Bitcoin Core from bitcoincore.org, verify the checksums and signatures, install the binaries, set prune=550 in bitcoin.conf to keep disk use low, then start bitcoind and wait for the first sync. The SaltVPS plan list matches Rock (6 vCPU / 16 GB / 240 GB) to a Bitcoin node.

In brief
  • Software: Bitcoin Core, from bitcoincore.org only, checked before use.
  • Pruned mode: prune=550 keeps only recent blocks; 550 MiB is the smallest value allowed.
  • Still a full node: a pruned node downloads and validates every block once.
  • Traffic: the first sync is the heavy part; watch the plan's monthly allowance.
  • Not mining: a node checks and relays blocks; mining is forbidden on SaltVPS servers.

How do you run a pruned Bitcoin node on a VPS?

For x86_64 Linux. Replace VERSION with the current release number shown on bitcoincore.org.

  1. Create a service user

    Run adduser --disabled-password bitcoin (or useradd -m bitcoin), so the node never runs as root.

  2. Download the release

    From bitcoincore.org/en/download, fetch bitcoin-VERSION-x86_64-linux-gnu.tar.gz, SHA256SUMS and SHA256SUMS.asc.

  3. Verify the files

    Run sha256sum --ignore-missing --check SHA256SUMS, then gpg --verify SHA256SUMS.asc after importing builder keys from the guix.sigs repository.

  4. Install the binaries

    Run tar xzf bitcoin-VERSION-x86_64-linux-gnu.tar.gz, then install -m 0755 -o root -g root -t /usr/local/bin bitcoin-VERSION/bin/*.

  5. Write bitcoin.conf

    As the bitcoin user, create ~/.bitcoin/bitcoin.conf with prune=550 and dbcache=2000 for a faster first sync.

  6. Start the node

    As the bitcoin user, run bitcoind -daemon. For start at boot, adapt the sample systemd unit shipped in the project's contrib/init folder.

  7. Follow the sync

    Run bitcoin-cli getblockchaininfo. Watch verificationprogress climb towards 1; pruned shows true.

What is the difference between a pruned and an archival Bitcoin node?

Both validate every rule; they differ in what they keep on disk afterwards.

Pruned and archival Bitcoin Core nodes compared on a VPS
ItemPruned (prune=550 or more)Archival (no prune)
Validates all blocksYesYes
Keeps old blocksNo, only the most recent onesYes, the whole chain
Serves old blocks to peersNoYes
Transaction index (txindex)Not availableAvailable
Wallet and own transactionsYes, for new activityYes, with full rescans
Disk usePrune target plus the chainstate databaseThe full chain plus the chainstate

Which VPS plan is best for a Bitcoin node?

Disk and traffic decide first; RAM speeds up the first sync. A pruned node keeps its block files near the prune target, but the chainstate database (the set of unspent outputs) still needs several gigabytes on top. An archival node needs room for the whole chain; check its current size before you pick a disk.

SaltVPS checked its plan list on 16 November 2026: Rock pairs 16 GB of RAM, 240 GB NVMe and 12 TB of traffic a month, at $15.00 a month on 12 months. Its RAM leaves room for a larger dbcache during the first sync. Slab (400 GB NVMe) and Dome (640 GB NVMe) have bigger disks. Compare them on the pricing page.

Should the node accept incoming connections?

It helps the network but is optional. Bitcoin Core listens on TCP 8333 by default, but a firewall that blocks the port limits it to outbound connections. To accept inbound peers, open the port with ufw allow 8333/tcp. Every SaltVPS server has one dedicated IPv4 and a routed IPv6 /64, so no port forwarding is needed.

Keep RPC closed to the internet. bitcoin-cli talks to bitcoind locally, and the firewall guide shows how to open only what you choose.

How do you keep a Bitcoin node healthy?

Update Bitcoin Core with each release, after the same checksum and signature checks. Stop it cleanly with bitcoin-cli stop, replace the binaries and start it again. Changing prune back to 0 later means downloading the chain again.

Apply the base hardening from the Linux VPS security guide before you run any wallet on the server. A Monero node follows the same pattern with monerod. Paying for the server itself in BTC is covered on buying a VPS with Bitcoin.

Bitcoin node on a VPS: questions

Is a pruned node a real full node?

Yes. It downloads and checks every block and transaction against the rules. It just deletes old block files after checking them.

How long does the first sync take?

It depends on CPU, disk, dbcache and peers. Expect hours to days; bitcoin-cli getblockchaininfo shows the progress.

Can I connect my wallet to a node on a VPS?

Yes, through an SSH tunnel or a server such as an Electrum server. Never expose RPC on a public address.

Can I run Lightning on a pruned node?

Some Lightning software supports pruned nodes; check its documentation. An archival node avoids the question.

What is the best way to run a Bitcoin node on a VPS in 2026?

Verified Bitcoin Core binaries, a dedicated user, pruning if the disk is small, and a systemd service so it restarts after a reboot.

Verdict
  • Running a Bitcoin node on a VPS takes verified Bitcoin Core, prune=550 and patience for the first sync.
  • Size for disk and traffic first; Rock's RAM helps the sync.
Sources (3)
  1. Download Bitcoin Core and verify the release — Bitcoin Core project (2026-11-16)
  2. Running a full node — bitcoin.org (2026-11-16)
  3. Sample bitcoin.conf and init scripts — Bitcoin Core project (2026-11-16)

Run your node on Rock

Rock gives 16 GB of RAM, 240 GB NVMe and a dedicated IPv4, paid in BTC or other coins.

From $2.25/mo on 12 months · no KYC

Configure