Skip to content

Guide · Nodes, bots and real disk sizes

Blockchain VPS paid in Bitcoin: run a node or a bot on a KVM server

Pay for your node's server in Bitcoin, Monero or another coin, the only payment methods Nymhost takes, and check first what fits: every size below comes from the requirements each project publishes, read on 18 November 2026. Cryptocurrency mining is forbidden on every plan.

Updated By Nymhost LLC14 min read

What fits

A blockchain VPS from Nymhost runs pruned Bitcoin and Monero nodes, a Lightning node, trading bots and services that read a chain through RPC. It does not run an unpruned Bitcoin node (about 740 GB), a full or archive Ethereum node (1.7 TB and more) or a Solana validator (256 GB of RAM): the largest disk is 400 GB on Global 24 and 320 GB on Offshore 16. Cryptocurrency mining is forbidden. Plans are Linux only, include no backups, and come with no DDoS protection beyond the default filtering of the data center network.

What a blockchain VPS can run, and what it cannot

Most of what people put on a VPS for cryptocurrency work is small: a pruned node, a Lightning node, a bot, an indexer that reads from a node or an RPC endpoint. Full chain histories are the large items, and the disk decides them. The table sets what each project publishes against the largest Nymhost disk, 400 GB.

Requirements published by each project, read 18 November 2026. bitcoin.org and the Anza docs show no update date; the Monero technical specification gives sizes as of 5 October 2026; ethereum.org was updated on 29 October 2026, with full-node sizes measured in September 2026. Largest Nymhost disks: 400 GB (Global 24) and 320 GB (Offshore 16).
What you runDisk it needsMemory it asksFits in 400 GB?Plan to start with
Bitcoin Core, full chainAbout 740 GB (bitcoin.org)2 GB minimumNoNot on Nymhost
Bitcoin Core, prunedAbout 7 GB at the smallest setting (bitcoin.org)2 GB minimumYesOffshore 4 (80 GB)
Lightning (LND) next to a pruned Bitcoin CoreLND: 5 GB minimum (Lightning Labs)LND: 2 GB minimum, quad-core CPUYesOffshore 8 (4 vCPU, 160 GB)
Monero, prunedAbout 105 GiB (113 GB) as of 5 October 2026 (Monero technical specification)4 GB or more for a node run as a service (Monero docs)YesOffshore 8 or Global 8 (160 GB)
Monero, full chainAbout 265 GiB (285 GB) as of 5 October 2026 (Monero technical specification)4 GB or more (Monero docs)Yes, with little room to growOffshore 16 or Global 24
Ethereum full node1.7 to 2.2 TB+ per execution client, plus 15 to 90 GB of beacon data; 4 TB NVMe advised (ethereum.org)16 GB minimum, 32 GB recommendedNoNot on Nymhost
Ethereum with rolling history expiryAbout 400 to 650 GB, not yet supported by Geth (ethereum.org)16 GB minimumNo: the whole disk or more, before beacon dataNot on Nymhost
Ethereum archive node2 TB+ (Geth) to 14 TB+ (Nethermind)Not statedNoNot on Nymhost
Solana validator (Agave)1 TB+ accounts, 1 TB+ ledger, 500 GB+ snapshots (Anza docs)256 GB or moreNoNot on Nymhost
Trading bot (Freqtrade)1 GB (freqtrade.io)2 GB, 2 vCPUYesGlobal 4 or Offshore 4

Disk first: why 400 GB decides what you can run

The two largest Nymhost plans set the ceiling:

  • Global 24: 8 vCPU, 24 GB RAM, 400 GB NVMe, 12 TB of traffic a month, $29.39 a month, in New York, Dallas, Los Angeles, London, Amsterdam or Frankfurt.
  • Offshore 16: 8 vCPU, 16 GB RAM, 320 GB NVMe, 20 TB of traffic a month, $20.49 a month, in Amsterdam, Reykjavik, Zurich or Bucharest.

On every plan the disk is NVMe, the RAM and the disk space are reserved for your VPS, and the vCPU are shared cores.

A full Bitcoin chain (about 740 GB) is close to twice the largest disk, and an Ethereum full node needs several times more, as the table shows. Chains only get longer, so a node that barely fits leaves you nowhere to go. For a terabyte or more, rent a dedicated server elsewhere or use a managed RPC endpoint, as the Ethereum section explains.

Traffic matters less than people expect. Nymhost quotas count outgoing data only, from 2 TB a month on the smallest plans to 20 TB on Offshore 16, and going over never triggers an automatic charge. bitcoin.org counts about 740 GB of download the first time a node starts, which an outgoing quota does not touch, then around 20 GB of download and, for well-connected nodes, 200 GB or more of upload a month. The upload counts, and Bitcoin Core's maxuploadtarget option (in MiB per day) can cap it. Compare the quotas of every plan on the Nymhost VPS plans page.

Bitcoin node on a VPS: run it pruned

A pruned Bitcoin Core node keeps only the most recent raw blocks, up to a limit you set, and deletes older ones. The setting is prune=N in bitcoin.conf, where N is the number of MiB allotted to raw block and undo data. bitcoin.org gives 550 as the smallest value above 0 and says pruning cuts disk use from over 750 GB to about 7 GB. This guide uses prune=10000 (about 10 GB) to keep more history, which also suits a Lightning node: Lightning Labs notes that aggressive pruning can slow LND down.

Pruning has costs. bitcoin.org lists it as incompatible with -txindex and -rescan, and the importwallet RPC is disabled, so a wallet added later cannot be rescanned against old blocks. Your node also stops keeping old blocks to send to other nodes.

For a bitcoin node VPS, Offshore 4 (2 vCPU, 4 GB RAM, 80 GB NVMe, $8.19 a month) leaves room for the chain state, the logs and a Lightning node later. bitcoin.org asks for 2 GB of RAM, so a 2 GB plan runs the node alone.

Download Bitcoin Core from bitcoincore.org (version 32.1 on 18 November 2026) with SHA256SUMS and SHA256SUMS.asc, import the signing keys of several developers from the bitcoin-core/guix.sigs repository, run the two checks below, and run the node as an ordinary user, not root. bitcoin-cli getblockchaininfo then reports pruned and size_on_disk. The RPC interface accepts only clients on the same machine by default, and Bitcoin Core's documentation says not to enable it over the public internet.

Check the download (commands from bitcoincore.org)
sha256sum --ignore-missing --check SHA256SUMS
gpg --verify SHA256SUMS.asc SHA256SUMS
~/.bitcoin/bitcoin.conf, first start and status
mkdir -p ~/.bitcoin
cat > ~/.bitcoin/bitcoin.conf <<'EOF'
prune=10000
# RPC stays local by default: do not add rpcbind or rpcallowip
EOF
bitcoind -daemon
bitcoin-cli getblockchaininfo
bitcoin-cli stop

Lightning node on a VPS

LND, the Lightning implementation from Lightning Labs, asks for at least 2 GB of RAM, a 1 GHz quad-core CPU and 5 GB of storage, on a 64-bit system and a good SSD rather than an SD card. It needs a Bitcoin backend, ideally Bitcoin Core on the same machine; the pruned node above works, and Neutrino mode runs without any local node. Because of the quad-core line, Offshore 8 (4 vCPU, 8 GB RAM, 160 GB NVMe, $13.49 a month) is the plan for Bitcoin Core and LND together.

Channel funds need more care than the node. LND's recovery guide says the 24-word seed recovers on-chain funds, while channel funds also need the static channel backup, the channel.backup file in .lnd/data/chain/bitcoin/mainnet. LND rewrites it each time a channel opens or closes, and it is safe to copy at any time. No Nymhost plan includes backups, so copy it off the VPS after every change. Do not back up channel.db instead: LND's guide warns that you can never know whether such a copy holds the latest channel state, and out-of-date state can cost the funds in those channels. Keep the seed off the server.

Export every channel backup to a file, then copy it to your own machine
lncli exportchanbackup --all --output_file=channel.backup

Monero node on a VPS

Start monerod with --prune-blockchain on the first sync. The Monero reference says pruning saves two thirds of the disk without degrading functionality, and Moneropedia says a pruned node downloads and stores a third of the chain. Pruning a full copy later does not shrink the file; the freed space is only reused. --sync-pruned-blocks accepts blocks that peers have already pruned and saves transfer. The trade-off is that your node helps new nodes sync less.

The Monero technical specification gives the blockchain at about 105 GiB for a pruned node and about 265 GiB for a full one, as of 5 October 2026, and the project's guide to running a node as a service advises 262.5 GiB or more of SSD for a pruned node, to leave room for growth, and 4 GB or more of RAM. Offshore 8 or Global 8 (160 GB) holds a pruned node today; Offshore 16 and Global 24 leave more headroom. The Monero VPS page has the free space plan by plan. Check what the synced node uses with du.

The RPC binds to 127.0.0.1 by default, because it gives full control over the node. To offer a public node, the reference requires --restricted-rpc and an explicit external bind; keep the full RPC private. On mainnet, 18080 is the peer port and 18081 the RPC port.

A node does not make you anonymous. Your VPS is still tied to an account number, its payments and its IP addresses in Nymhost's billing records. To pay for the server itself in XMR, see pay for a VPS with Monero; a Monero top-up is credited after 10 confirmations.

Pruned Monero node in the background (commands from the monerod reference)
monerod --prune-blockchain --sync-pruned-blocks --detach
tail -f ~/.bitmonero/bitmonero.log
du -sh ~/.bitmonero
monerod exit

Ethereum and Solana: what does not fit

An Ethereum node is two programs, an execution client and a consensus client. ethereum.org lists full-node sizes measured in September 2026: 1.7 TB+ for Nethermind and Erigon, 1.8 TB+ for Besu and Geth, 2.2 TB+ for Reth, plus 15 to 90 GB of beacon data. Its minimum hardware is 16 GB of RAM (32 GB recommended) and a 4 TB NVMe SSD, and its recommendation for validating rises to 8+ cores and 64 GB of RAM. None of it fits on a 400 GB disk, and a validator needs that full node underneath.

Solana is further out of reach. Anza's requirements for an Agave validator start at 12 cores and 24 threads, 256 GB of RAM and about 2.5 TB of NVMe split between accounts, ledger and snapshots, on a 1 Gbit/s symmetric link if unstaked and 2 Gbit/s or more if staked. The largest Nymhost plan has 24 GB of RAM.

What works instead: read these chains through a managed RPC endpoint from another provider, and run on the VPS the program that uses the data, such as a bot, an indexer for your own contracts, an alert service or a backend that holds no keys. Other chains publish their own requirements; check them against the table above before you order.

Trading bots and chain-reading services

Bots are the lightest use. Freqtrade, a free and open-source crypto trading bot written in Python, recommends a Linux cloud instance with at least 2 GB of RAM, 1 GB of disk and 2 vCPU. Global 4 ($6.39 a month) or Offshore 4 ($8.19) meets that with 2 vCPU and 4 GB. Freqtrade's own page warns against risking money you are afraid to lose; that applies to any bot. Telegram bots, price alerts, wallet watchers and small indexers in Python or Node.js need about the same.

Pick the city by where the exchange's API servers are, and measure it yourself: Nymhost publishes no latency figures. The nine cities are Amsterdam, Reykjavik, Zurich, Bucharest, New York, Dallas, Los Angeles, London and Frankfurt. Time a few API calls from a 1-month VPS before you commit to 12 months. The crypto trading bot VPS guide gives the Freqtrade install, the API key settings and a script for that test.

Limits to know:

  • Linux only. No Windows and no RDP, so Windows-only trading terminals will not run.
  • Shared resources. The vCPU are shared cores and the 1 Gbit/s port is shared with the VPS on the same host; RAM and disk are reserved.
  • No extra DDoS protection. A bot that only makes outgoing calls exposes little; a public service is on its own.
  • Exchange API keys. Give a bot reading and trading rights only, never withdrawal rights, and keep its keys out of your code repository.

Which plan for which node

Size the plan for the heaviest program, then leave room for growth. Lengths are 1, 3, 6 or 12 months, paid ahead from your crypto balance, with 10%, 20% or 30% off the longer ones; there is no hourly billing.

Nymhost plans and 1-month prices of 18 November 2026 (vCPU / RAM / NVMe).
WorkloadPlanvCPU / RAM / NVMe1 month
Pruned Bitcoin nodeOffshore 4 or Global 42 / 4 GB / 80 GB or 65 GB$8.19 / $6.39
Pruned Bitcoin node with LNDOffshore 84 / 8 GB / 160 GB$13.49
Pruned Monero nodeOffshore 8 or Global 84 / 8 GB / 160 GB$13.49 / $19.19
Trading bot (Freqtrade)Global 4 or Offshore 42 / 4 GB / 65 GB or 80 GB$6.39 / $8.19
Several small services togetherGlobal 6 or Offshore 82 / 6 GB / 120 GB or 4 / 8 GB / 160 GB$9.59 / $13.49
Largest diskGlobal 24 or Offshore 168 / 24 GB / 400 GB or 8 / 16 GB / 320 GB$29.39 / $20.49

Nymhost plans for nodes and bots

Live prices for both ranges of the Nymhost VPS offer. Offshore plans run in Amsterdam, Reykjavik, Zurich and Bucharest; Global plans in New York, Dallas, Los Angeles, London, Amsterdam and Frankfurt.

Nymhost Offshore

Amsterdam · Reykjavik · Zurich · Bucharest

Offshore 1

$3.09/ month

3 mo $8.346 mo $14.8312 mo $25.95

  • 1 vCPU
  • 1 GB RAM
  • 20 GB NVMe
  • 2 TB traffic
Deploy Offshore 1

Offshore 2

$4.89/ month

3 mo $13.206 mo $23.4712 mo $41.07

  • 1 vCPU
  • 2 GB RAM
  • 40 GB NVMe
  • 4 TB traffic
Deploy Offshore 2

Offshore 4

Best balance

$8.19/ month

3 mo $22.116 mo $39.3112 mo $68.79

  • 2 vCPU
  • 4 GB RAM
  • 80 GB NVMe
  • 8 TB traffic
Deploy Offshore 4

Offshore 8

$13.49/ month

3 mo $36.426 mo $64.7512 mo $113.31

  • 4 vCPU
  • 8 GB RAM
  • 160 GB NVMe
  • 12 TB traffic
Deploy Offshore 8

Offshore 16

$20.49/ month

3 mo $55.326 mo $98.3512 mo $172.11

  • 8 vCPU
  • 16 GB RAM
  • 320 GB NVMe
  • 20 TB traffic
Deploy Offshore 16

Nymhost Global

New York · Dallas · Los Angeles · London · Amsterdam · Frankfurt

Global 2

$3.19/ month

3 mo $8.616 mo $15.3112 mo $26.79

  • 1 vCPU
  • 2 GB RAM
  • 40 GB NVMe
  • 2 TB traffic
Deploy Global 2

Global 4

$6.39/ month

3 mo $17.256 mo $30.6712 mo $53.67

  • 2 vCPU
  • 4 GB RAM
  • 65 GB NVMe
  • 2 TB traffic
Deploy Global 4

Global 6

$9.59/ month

3 mo $25.896 mo $46.0312 mo $80.55

  • 2 vCPU
  • 6 GB RAM
  • 120 GB NVMe
  • 6 TB traffic
Deploy Global 6

Global 8

$19.19/ month

3 mo $51.816 mo $92.1112 mo $161.19

  • 4 vCPU
  • 8 GB RAM
  • 160 GB NVMe
  • 12 TB traffic
Deploy Global 8

Global 24

$29.39/ month

3 mo $79.356 mo $141.0712 mo $246.87

  • 8 vCPU
  • 24 GB RAM
  • 400 GB NVMe
  • 12 TB traffic
Deploy Global 24

Prices in US dollars, checked on 18 November 2026. Paid from a crypto balance (minimum top-up $25); 3, 6 and 12 months save 10, 20 and 30%. Every plan: KVM, root over SSH, 1 dedicated IPv4 + /64 IPv6, shared 1 Gbit/s port.

Run it safely: keys, RPC, backups and DDoS

  • RPC stays private. Bitcoin Core accepts RPC only from the same machine by default, and Monero binds it to 127.0.0.1. Leave it that way, and reach it from your computer through an SSH tunnel or a WireGuard VPN for your RPC port.
  • Keys and seeds stay off the VPS. A server is a machine someone else hosts. If a service needs a hot wallet, keep only a small balance in it.
  • Log in with an SSH key. Add a public key at checkout and password login stays off.
  • Back up what you cannot rebuild. No plan includes backups, and a reinstall erases the disk. A chain can be synced again; a channel backup, a wallet file or a bot's configuration cannot. Copy them off the server.
  • Expect to handle attacks yourself. No DDoS protection is promised beyond the default filtering of the data center network, and a node with a public IP and an open peer port is reachable by anyone.

Allowed and forbidden on a Nymhost node

The acceptable use policy applies to every plan, and cryptocurrency mining is forbidden whatever the coin or the software.

Forbidden, VPS suspended

  • Cryptocurrency mining, including mining dressed up as a node or validator
  • Spam, phishing, carding and other fraud
  • DDoS and other attacks, scanning or brute-forcing other people's systems
  • Malware or botnet control
  • Service to sanctioned people or companies

Fine

  • Pruned Bitcoin and Monero nodes
  • Lightning nodes
  • Trading bots, alert bots and indexers
  • Tor relays, exit relays included

Pay for a node VPS in BTC or XMR

A node operator usually holds coins already, and crypto is the only way to pay for the server: no card, PayPal or bank transfer. Bitcoin goes on-chain, since the checkout has no Lightning option, and is credited after 2 confirmations, about 20 minutes on the checkout; Monero takes 10 confirmations, and a block explorer shows neither its sender nor its amount. Each top-up is $25 or more into a balance that never expires, so a year of Offshore 8 for Bitcoin Core and LND ($113.31, or $9.44 a month) can be paid at once, and the checkout shows the exact amount to send when you pay for a node server in BTC or another coin. The no-KYC VPS page lists what Nymhost keeps about you.

Blockchain VPS: nodes, mining and bots

Can I run a full Bitcoin node on a VPS?

Yes, pruned. Bitcoin Core in pruned mode keeps only the most recent blocks, about 7 GB at the smallest setting according to bitcoin.org. The whole chain, about 740 GB, does not fit on any Nymhost plan: the largest disk is 400 GB.

Can I run an Ethereum node on Nymhost?

No. ethereum.org lists 1.7 TB or more for a full node's execution client alone and advises a 4 TB NVMe drive, ten times the largest Nymhost disk. Use a managed RPC endpoint for Ethereum data and run your bot or indexer on the VPS.

Can I mine crypto on a Nymhost VPS?

No. Cryptocurrency mining is forbidden on every plan, whatever the coin or the software, and a VPS used for it is suspended. That includes a miner presented as a node or a validator. Nodes, Lightning and bots are fine.

Can I run a trading bot on a Nymhost VPS?

Yes, on Linux. Freqtrade asks for 2 GB of RAM, 1 GB of disk and 2 vCPU, which Global 4 or Offshore 4 covers. Windows-only trading terminals will not run, because Nymhost offers no Windows and no RDP.

Do you protect nodes against DDoS attacks?

No protection is promised beyond the default filtering of the data center network. Keep RPC ports closed, expose only the peer port your node needs, and do not count on the VPS to absorb a large attack.

Does running my own node make me anonymous?

No. A node checks the chain for you, but the VPS still belongs to an account that billing links to its orders, its IP addresses and the transaction ID of each payment, and payments on public blockchains stay visible.

Pick a plan for your node

Pruned Bitcoin, Lightning, Monero or a bot: start on a 1-month plan, measure the sync, then choose a longer length.

Sources

  1. Running a full node (disk, bandwidth, pruning, maxuploadtarget) bitcoin.org
  2. Download Bitcoin Core (version 32.1, verification steps) Bitcoin Core
  3. JSON-RPC interface: security Bitcoin Core
  4. bitcoin.conf configuration file Bitcoin Core
  5. getblockchaininfo RPC (size_on_disk, pruned) Bitcoin Core
  6. Run a node (hardware, disk size by client, history expiry) ethereum.org
  7. Agave validator requirements Anza
  8. Run LND (hardware requirements, backends, pruning) Lightning Labs
  9. LND disaster recovery (static channel backup) Lightning Labs
  10. LND recovery guide (seed, channel.backup, exportchanbackup) Lightning Labs
  11. Moneropedia: pruning The Monero Project
  12. monerod reference (--prune-blockchain, --sync-pruned-blocks, RPC binding, ports) The Monero Project
  13. Freqtrade documentation (hardware recommendation, risk warning) Freqtrade
  14. Monero technical specification (blockchain size, pruned and full) Monero Docs
  15. Running a Monero node via systemd (disk and RAM advice) Monero Docs