01
Name the client and role before choosing hardware
Specify the network, client software, version and required role: a private node, a public RPC service or a history-heavy installation. These are purchasing requirements, not interchangeable labels. Check the project's current official requirements before ordering; this page does not publish fixed capacity claims for every chain.
Build the shortlist from memory, CPU demand, current data, growth and the operations needed during upgrades or recovery. Account for the extra services you intend to run alongside the client. A model that fits an initial dataset is not automatically suitable for the retention policy you want.
02
Compare storage allocation and network needs together
The following are candidates to check against upstream requirements, not certified node configurations. Raw NVMe totals precede redundancy, filesystem overhead and working reserves.
- Ryzen 9 5950X: 128 GB RAM and 4 TB raw NVMe on a 1 Gbps port. Consider it where the complete requirement fits this allocation.
- EPYC 7513: 256 GB listed ECC memory, four NVMe devices and a 10 Gbps port. Compare it when disk layout and network requirements justify moving beyond Ryzen.
- EPYC 9554: 768 GB RAM and 30.72 TB raw NVMe. The larger allocation needs a workload justification; it is not a promise to fit every archival dataset.
03
Separate a rented host from a managed node service
You install the client, maintain its configuration, follow upgrades and decide how access is controlled. RPC administration, client monitoring and recovery are not included managed services. An operating-system installation does not establish that a node is synchronized or ready for your application.
Keep any client credentials or signing material under your own control; do not put secrets in a sales enquiry. If public access is required, document authentication, abuse handling and protection needs. Confirm any separately quoted network service rather than assuming an RPC-specific protection profile or private peer network is included.
04
Plan delivery, growth and replacement separately
Confirm the exact drives and write-endurance requirement if your client has a sustained-write workload. Decide how data and configuration will be recovered after host replacement, and leave room for the chosen procedure. No synchronization duration or sustained disk rate is promised by the catalogue.
Choose a region and confirm the model's delivery window before scheduling a cutover. Budget separately for hardware rental and any external services the node depends on. Crypto deposits fund a USD ledger for rental charges; they do not provide a node account, client installation or operational management.
Direct answers
Questions before you order
Is this a managed RPC or validator service?
No. The offer is dedicated hardware for software you operate. Confirm client requirements and arrange administration, monitoring and recovery separately.
Does paying in BTC mean Bitcoin Core is installed?
No. Payment method and server workload are independent. The Bitcoin payment page explains funding; the node guide covers preparation for running your own software.