NulNetMonero node on a VPS
Run monerod on a no-ID KVM: pruned or full chain, P2P on 18080, optional Tor/I2P, wallet RPC kept local. Crypto invoice, root access.
نص المقال الطويل بالإنجليزية. الواجهة والكتالوج والدفع مترجمة.
Why people run a node
What is Monero: Monero is digital cash with privacy on by default — stealth addresses, ring signatures and RingCT hide sender, receiver and amount on every transaction, where transparent chains leave addresses linkable. Verification is the point of holding the coin: a wallet backed by your own node checks the consensus rules itself instead of asking a stranger's server whether a balance is real.
The VPS pattern covers two roles. As a private backend, monerod serves your wallets — the scan that light wallets hand to a third-party view-key service stays on hardware you control instead. As a public remote node, it lets GUI and CLI wallets sync without downloading the chain, with inbound P2P open so other people's nodes can bootstrap from yours. Same daemon either way; the difference is which ports you publish.
VPS from $3* (fund $50+), storage 1–5 TB NVMe from $24/mo annual-eff, dedicated with IPMI from $30.80/mo. Crypto invoice, no KYC.
Launch nowFacts from the Monero project
Monero: run a node on a VPS is the official VPS walkthrough: allow port 18080, pull the Linux binaries from Monero downloads (CLI / GUI), extract, then start ./monerod (add --detach to background it). Monero user guides documents wallets, remote-node GUI setup, Tor and I2P transport, and the systemd unit.
| Topic | Practical note |
|---|---|
| P2P | TCP 18080 — required for inbound peers on the Monero network |
| RPC | Default wallet RPC binds to localhost; tunnel over SSH when the wallet lives elsewhere |
| Prune | Official CLI/GUI pruning keeps roughly ⅓ of the chain on disk |
| Roles | Private wallet backend, public remote node, or both |
| Privacy add-ons | Optional Tor/I2P for node and wallet traffic (project user guides) |
| Hosting bill | One crypto invoice covers any NulNet SKU — BTC, USDT, ETH, SOL, LTC, TRX |
Playbook
- Ranger or Warden for a pruned private node. Vanguard / Sentinel or dedicated when you publish a remote node others will hammer.
- Follow Monero: run a node on a VPS: open 18080, install from Monero downloads (CLI / GUI), start monerod.
- Iceland or Romania are common racks. Amsterdam if most of your peers sit on EU IXes.
Sizing the box to the role
A private pruned node is a small constant load: one core of sync work after initial bootstrap and RAM for the DB cache — Ranger (4 vCPU / 8 GB, $12.50 list, $10.00 annual-eff) is comfortable, Sentry (2 vCPU / 4 GB, $7.50 / $6.00) is the floor. A public remote node is a traffic role: dozens of concurrent wallets, so RAM, NVMe endurance and the port matter more — Vanguard (8 vCPU / 24 GB) or Sentinel (12 vCPU / 32 GB, $33.50 list) on the VPS line, or Shield metal ($38.50 list, $30.80 annual-eff) with whole cores and IPMI. Size the disk against the current chain length the project publishes before ordering; if terabytes of related archives pile up beside the node, the NVMe storage ladder keeps them off the system disk.
What you get vs what you run
The host sells the KVM — root, unmetered uplink, included DDoS filtering — and stays out of the daemon: no managed monerod, no curated peers. You choose prune versus full, decide whether RPC stays on localhost or the node becomes public, and own the config file with its Tor or I2P bridges. One asymmetry to keep in mind: other people's wallet traffic through your public node is their threat model, not a service level you sold them. The checkout side stays what it is everywhere else — sixteen coins, XMR first-class, no KYC step.
Is a pruned node enough for a wallet?
Yes for normal spend and receive — pruning drops old block bodies, not the consensus data your wallet verifies. Archival research and block explorer work want the full chain instead.
Do you manage monerod for me?
No. You get root and install the official binaries yourself; upgrades, flags and restarts are yours. The host's job ends at the KVM, the port and the invoice.
Which ports does a Monero node need?
TCP 18080 for P2P if you want inbound peers. Keep the RPC port bound to localhost and tunnel over SSH unless you deliberately publish a remote node.
Can the node run over Tor or I2P?
Yes. The project's user guides cover both transports, and the VPS does not block them — the daemon's own config decides what announces where.
How do I pay for the node?
Any of the sixteen checkout coins settles the invoice; XMR keeps the payment rail consistent with the workload, USDT-TRC20 keeps it dollar-stable. Either way no ID enters the flow.
Ready to launch?
Build the box — VPS, storage or bare metal — create the password, pay the invoice that follows.