CryptoServers

Bitcoin full node on offshore hardware

Run Bitcoin Core with the full UTXO set and an open port 8333 — no node-as-a-service middleman, no consensus you didn't verify yourself.

No KYC, ever DMCA ignored No traffic logs Live in 60 seconds
1 Tbps
DDoS absorption
41s
Median deploy
3
Recommended locations
$39.99
Entry plan / month
Built for the workload

Why Bitcoin full node runs better here

Specific technical alignment, not generic copy. Each point below is something the workload needs and we provide by default.

Inbound 8333 open by default — your node serves the network, not just queries it.
NVMe everywhere. IBD finishes in 3–5 days on Business+, in 1–2 days on EPYC dedicated.
IPv4 + /64 IPv6 with full p2p reachability. Tor companion (.onion peer) supported.
No connection caps on outbound peer selection. Run the full 125 peer maximum.
Zero deep-packet inspection. No "node operator" registration, no chain-watching layer above us.
Workload notes

What you should know about Bitcoin full node on Cryptoservers

Sized for the chain weight as it stands now: ~700 GB pruned, ~900 GB unpruned with txindex. NVMe is mandatory — the IBD write amplification on rotational disks takes weeks. We ship NVMe across every plan tier; vps-business at 240 GB suffices for pruned, vps-pro at 400 GB lets you keep txindex enabled for analytics. Inbound port 8333 is open by default — every plan ships full IPv4+IPv6 reachability so your node helps the network.

For a node you intend to run for a long time without re-IBD'ing, ded-shield with 2× NVMe in mirror is the most resilient option. We don't restrict outbound peers, don't shape p2p traffic, and don't intercept SSL. Bring your own bitcoind config; we host the wire.

Sysadmin FAQ

Bitcoin full node — questions answered

How much disk do I really need for Bitcoin Core today?
For a pruned node: 5–10 GB depending on prune setting. For a normal node (current chainstate + blocks): ~700 GB. With txindex enabled: ~900 GB. We size to growth — vps-pro's 400 GB NVMe holds a pruned node + Lightning + a Bitcoin metrics layer comfortably.
How long does initial block download take here?
On vps-business with EPYC + DDR5 + Gen4 NVMe: typically 3–4 days. On ded-shield (single-socket EPYC, 2× Gen4 NVMe in software RAID): under 36 hours. Network is rarely the bottleneck — it's signature verification and UTXO writes.
Can I peer my node over Tor (.onion) too?
Yes — Tor is allowed and we don't restrict outbound. Configure bitcoind to listen on .onion via your local Tor instance; your node will accept incoming peers via both clearnet and Tor.
Will you host my Lightning node alongside the Bitcoin node?
Yes — see the lightning-node solution. Same box can run both; many customers do. We just recommend separate UTXO management between bitcoind's wallet and the LN signer.
Do you collect any data on what my node is doing?
No. We don't inspect the wire, don't fingerprint p2p traffic, and don't maintain any "list of node operators" you're aware of. The plan is rented hardware; what you run on it is your business per /privacy/.

Bitcoin full node — deploy in 60 seconds

No email, no ID, no account. Pick a plan, pay in crypto, get root.