Use case · Crypto

Crypto node hosting. Verify, don't trust — 24/7.

"Don't trust, verify" is the whole point of running your own node — and it stops meaning much if the machine lives in a cloud account tied to your passport. On VPSRento the node runs 24/7 on unmetered bandwidth, the account is a token, and the VPS itself is paid in crypto. Nobody can map the operator because nobody collected the operator.

  • Unmetered on SV-Pro
  • Pay with XMR
  • 99.9% SLA · 24/7
  • Full root — any chain
deploy — monero node, zurich
Why this use case

The infrastructure should be as private as the asset

A third-party node is a third party. Every wallet query, every broadcast, every balance check flows through an operator who can observe it — which is why "run your own node" became gospel. But most node operators then rent the machine from a cloud giant that demands a card, a name and an email, and logs everything the node does.

VPSRento closes that gap. The account is a 24-character token — no email, no name, no phone. Payment is crypto-only via Paymento, and if you pay in XMR the ledger itself reveals neither sender nor amount. The jurisdiction holding the disks is one you chose deliberately. No activity logs are kept on our side either; we can't sell what we never had.

And the workload is taken seriously: staking validators need uptime, not excuses, so a 99.9% SLA with automatic credits comes standard. Full nodes need bandwidth, so SV-Pro and above are unmetered on a 1 Gbps port — initial sync and peer serving move hundreds of gigabytes without a meter running.

What the box comes with

  • Unmetered 1 Gbps on SV-Pro+. Sync once, serve peers forever — no transfer cap to plan around.
  • 99.9% SLA, credits automatic. Validators sleep better; hardware RAID and daily offsite snapshots back it up.
  • No KYC + crypto-only. XMR for maximum privacy; BTC, ETH, LTC, USDT and SOL also accepted.
  • NVMe sized to the chain. 120 GB on SV-Pro, 240 GB on SV-Max, 480 GB on SV-Ultra.
  • Disk encryption on all nodes. The host layer stays quiet even in a hardware-handling scenario.

"Running 3 full nodes here. Pay with Monero, renews itself, zero emails in my inbox because they never had it."

sat0shi_fan crypto node operator
Setup pointers

From deploy to synced node in one evening

The short version — pick the plan by chain size, harden the base, and let the unmetered port do the boring part.

# Debian 13 — Monero full node $ apt install monero $ monerod --data-dir /var/lib/monero \ --rpc-bind-ip 127.0.0.1 --restricted-rpc

Checklist

  • Size NVMe to the chain. 120 GB fits most chains on SV-Pro; a Bitcoin full node wants SV-Max (240 GB) or SV-Ultra (480 GB) today.
  • Harden first: the VPS hardening checklist — SSH keys, firewall, fail2ban — twenty minutes before the daemon ever starts.
  • Bind RPC to localhost and tunnel wallets over SSH, or put it behind WireGuard — your node, your eyes only.
  • Snapshot wallet-critical data. Daily offsite snapshots are $1.99/mo — validators should treat them as part of the staking setup.
  • Pay with XMR at checkout if you want the payment trail as quiet as the node itself.

What this is not

  • Not a mining rig. Mining is prohibited on shared nodes per the AUP — it steals CPU from neighbours, and a VPS is the wrong economics for it anyway.
  • Not key custody. We sell the metal. Wallets, seeds and validator keys stay with you — self-custody is the entire point.
  • Not a guarantee against your own mistakes. An open RPC port or an unpatched daemon is on you. Harden first, then sync.

Node hosting is the workload where our model makes the most sense: the value of the machine is privacy and uptime, and both are things we sell structurally rather than promise contractually. The token account cannot be subpoenaed for a name it never stored. The XMR payment cannot be traced to a person. The jurisdiction cannot be leaned on by a foreign civil letter. The node just sits there, syncing.

Worth knowing: for payments, the pay-for-VPS-with-crypto guide walks through BTC vs XMR vs USDT tradeoffs and how the Paymento checkout works step by step.
Recommended setup

SV-Pro for most chains, SV-Max for Bitcoin

Two numbers decide the plan: NVMe for the chain history, and bandwidth for the peers. Unmetered covers both.

Node profile Plan NVMe Switzerland Iceland
Light client / Electrum serverSV-Core · 2 vCPU · 4 GB60 GB$12.99$12.49
Full node (most chains)SV-Pro · 4 vCPU · 8 GB120 GB$23.99$22.99
Bitcoin node / validatorSV-Max · 8 vCPU · 16 GB240 GB$44.49$42.49

Full specs on the Linux VPS page; live per-location prices on the Zurich and Reykjavik location pages. Quarterly −10% · 6 months −30% · annual −50% — best value (e.g. SV-Pro: $19.99/mo → $9.99/mo equivalent billed annually).

FAQ

Crypto node hosting, answered

You cannot pay any other way — VPSRento is crypto-only. BTC, XMR, ETH, LTC, USDT (TRC-20/ERC-20) and SOL are processed by Paymento; we never touch card rails. For maximum privacy choose XMR: the ledger reveals neither sender nor amount, so even the payment trail says nothing about who runs the node.

Size NVMe to the chain. SV-Pro at $19.99/mo — 4 vCPU, 8 GB RAM, 120 GB NVMe and unmetered 1 Gbps — runs Monero, Lightning and most chain nodes with room to spare. A Bitcoin full node has outgrown 120 GB, so go SV-Max at $36.99/mo (240 GB) or SV-Ultra at $69.99/mo (480 GB). Unmetered bandwidth matters on all of them: initial sync and peer serving can move hundreds of GB.

No. Mining is prohibited on shared nodes per the AUP — it steals CPU from neighbouring customers, and a VPS is the wrong price-performance tool for it anyway. Running full nodes, staking validators, Lightning and Electrum servers is explicitly allowed and is one of our most common workloads. Verify, don't mine.

Your node, syncing in 55 seconds.

Pay with XMR, get root on a clean IP, and infrastructure whose operator never learned your name.