Skip to main content

System Requirements

Running a XPHERE Node (XEN) requires relatively higher hardware specifications compared to the ones for Ethereum or other blockchains, because XEN has to validate blocks generated by the full-fledged Consensus Nodes equipped with enterprise-grade hardware.

For XPHERE Nodes, the following minimum specifications are recommended.

This page sizes Endpoint Nodes

The figures below apply to the Endpoint Node client (XEN). Main Chain validators have their own, higher sizing — see Validator Node.

H/W Specification​

Cloud VM​

Minimum Hardware Requirements​

ComponentMinimumRecommended
vCPU816
Memory (RAM)32 GiB64 GiB
Storage TypeNVMe SSD (no HDD)NVMe SSD
Storage Capacity2 TB4 TB+
Disk Bandwidth250 MB/s500 MB/s+
IOPS5,00010,000+
Network1 Gbps10 Gbps

These are operational recommendations from the XPHERE Foundation. The XEN client does not check or enforce any of them at startup — an undersized machine will start, then fall behind or fill its disk.

Bare-metal Machine​

Any physical machine meeting or exceeding the minimum requirements above is suitable for running a XPHERE Node.

Storage Requirements​

  • Type: NVMe SSD only (HDDs are not supported)
  • Capacity: At least 2 TB free space (4 TB+ recommended for long-term operation)
  • Disk Bandwidth: 250 MB/s or higher
  • IOPS: 5,000 or higher
  • Filesystem: ext4 or xfs recommended

Note: Storage must be dedicated to blockchain data. Do not share with OS or other applications.

How Large the Chain Actually Is​

Both figures below are measurements you can reproduce, not projections. Check them before you provision — they only grow.

Published chain data, compressed. The Mainnet chaindata snapshot listing reports the archive size in bytes:

curl -s https://package.x-phere.com/mainnet/chain-data
{"files":[{"prefix":"mainnet","name":"xphere-mainnet-chaindata-20260804095117.tar.gz",
 "lastModified":"2026-08-04T08:26:48.560Z","size":"246430233094"}]}

That is 246,430,233,094 bytes — roughly 230 GiB compressed for the snapshot published on 2026-08-04. The extracted database is larger than the archive, and a running node keeps growing past whatever the snapshot captured.

Chain height and block rate. Ask a public Endpoint Node for the current head:

curl -s -X POST https://rpc.x-phere.com -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"xp_blockNumber","params":[],"id":1}'
{"jsonrpc":"2.0","id":1,"result":"0x2b0fa06"}

0x2b0fa06 is block 45,152,774 (2026-08-05). Comparing block timestamps 100,000 blocks apart gives an average of about 1.0–1.1 seconds per block, so the chain adds on the order of 80,000 blocks per day.

Recent Mainnet blocks report a size of roughly 2.9 KB each, which puts block data alone near 230 MB/day. Treat that as a floor rather than a disk budget: a node also stores receipts, the state trie, and indexes, and those dominate on-disk usage.

Provision headroom and monitor disk usage

A volume sized to today's chain data will fill up. Provision at or above the capacity in the table, alert on free space for the data volume, and plan expansion well before the volume fills.

All specifications above are minimum requirements for stable operation. Higher specs are strongly recommended for mainnet or production use.

Operating System​

A modern 64-bit Linux distribution on x86-64 (amd64) hardware is required.

Only a Linux x86-64 build is distributed

The single published package is xen-v0.9.0-amd64-linux.tar.gz. No macOS build and no ARM build is distributed. There is no download that yields a XEN binary for macOS.

bin/xen from the package is a dynamically linked x86-64 ELF binary, so it needs a glibc-based Linux host. Confirm what you downloaded before planning around it:

tar -xzf xen-v0.9.0-amd64-linux.tar.gz
file xen-v0.9.0-amd64-linux/bin/xen
ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked,
interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0

The XEN client source is not currently published, so building your own binary for another platform is not an option today. Run the distributed Linux x86-64 package, and verify it against the published SHA256 checksum before running it.

See Also​