NulNetBitcoin Node VPS — bitcoind, No KYC, USDT or BTC
Run Bitcoin Core on a no-ID VPS: a pruned node fits Ranger ($12.50 list), archival wants Storage or metal. Live-rate invoice in USDT or BTC.
Download Bitcoin Core from the official source, keep blocks and chainstate on NVMe, and open port 8333 when you want the node to accept inbound peers. A pruned node fits Ranger; archival and big dbcache want Vanguard, Sentinel or dedicated metal.
What people actually run
One daemon does the work: Bitcoin Core with Bitcoin Core: running a full node as the field guide. The variables that matter on a VPS are disk (blocks and chainstate want NVMe), prune (a bounded node versus a full archive), inbound peers (port 8333 open or closed), and initial block download time, which RAM and disk end summarize. Billing has its own logic: pay the invoice in BTC at a live rate, or in USDT when the hosting bill should not swing with the very coin the node validates.
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 nowPlaybook
- Pruned: Ranger. Archival or heavy dbcache: Vanguard / Sentinel or Dedicated.
- Install from Bitcoin Core. Keep blocks on NVMe.
- Romania or Iceland are common. Amsterdam if peers are at EU IXes.
Sizing and placement
A pruned node is a modest tenant: 4 GB RAM and NVMe headroom carry it, which puts Ranger (4 vCPU / 8 GB, $12.50 list, $10.00 annual-eff) in the comfortable zone and Sentry (2 vCPU / 4 GB, $7.50 / $6.00) at the floor. An archival node grows without bound — check the current chain size on the project's site before ordering, then prefer Sentinel (640 GB NVMe) or dedicated metal, where the storage ladder and whole-core units sit on the same account. Placement follows peers: Bucharest or Reykjavik for a personal node, Amsterdam when connection counts and EU exchange latency matter. Every tier ships ECC RAM, and the checkout stays token-or-email with no ID.
Do I have to use assumevalid or my own flags?
Your node, your flags — the host never touches bitcoind config. Root means every setting, from prune size to peer limits, is yours to argue with.
Can I pay the node's hosting in Bitcoin?
Yes. The invoice quotes BTC at a live rate; choose USDT when you want the bill dollar-stable instead of riding the same market the node validates.
KYC to run a node?
No. Signup takes a token or an email plus a 12-character password, then a crypto invoice — no documents, no phone, no card.
Does the VPS line accept inbound connections on 8333?
Yes. Ports are yours to open; the unmetered uplink absorbs peer traffic, and included DDoS filtering handles the junk that public nodes attract.
Primary sources
Ready to launch?
Build the box — VPS, storage or bare metal — create the password, pay the invoice that follows.