A Sui node holds 459 GB today; even 16 TB lasts under two years
Sui full nodes need 128 GB RAM and 4 TB NVMe. Without pruning a full node can pass 7 TB.
A 4 TB disk cannot be timed yet
Full node
Official requirements
- CPU
- 8 physical cores / 16 vCPU
- RAM
- 128 GB
- Disk
- 4 TB NVMe
- Bandwidth
- not published
- Source
- Sui docs: full node (undated, checked 2026-11-12)
Data and growth
- Data now
- 459 GB Measured
PublicNode snapshot (1.83.1, uncompressed), 14 Nov 2026 - Growth
- — No data
Not measured yet: we record this snapshot's size every 6 hours and show growth once we have 10 days of history
Snapshot size history: 3 points since 11 Nov 2026
Bloat clock (disk 90% full at today's growth)
What it costs
Server: Hetzner AX102 (16 cores, 128 GB DDR5 ECC, 2 × 1.92 TB NVMe) at from €159/month, price page (2026-11-12)
Home build: not realistic for this node (needs more cores, RAM or disk than a mini PC holds).
Validator
Official requirements
- CPU
- 24 cores / 48 vCPU
- RAM
- 128 GB
- Disk
- 4 TB NVMe
- Bandwidth
- 1 Gbit/s
- Source
- Sui docs: validator (undated, checked 2026-11-12)
Data and growth
- Data now
- 379 GB Measured
PublicNode snapshot (1.83.1, uncompressed), 15 Nov 2026 - Growth
- — No data
Not measured yet: we record this snapshot's size every 6 hours and show growth once we have 10 days of history
Snapshot size history: 14 points since 12 Nov 2026
Bloat clock (disk 90% full at today's growth)
What it costs
Server: Hetzner AX162 (48 cores, 128 GB DDR5 ECC, 2 × 1.92 TB NVMe) at from €319/month, price page (2026-11-12)
Home build: not realistic for this node (needs more cores, RAM or disk than a mini PC holds).
Also on the Network Desk for Sui
How this works and where the data comes from
Data size. Where possible we read the uncompressed size of the latest node snapshot that PublicNode publishes for that chain and client (refreshed every few hours to weekly by them; we check every 6 hours). For Bitcoin we use the total block-data series from blockchain.com plus the documented chainstate size. Otherwise we use the figure in the official docs, with its date.
Growth. Best available, in this order: the change in snapshot size over at least 10 days (we build this history ourselves, so it appears after two weeks); Bitcoin's 60-day block-data growth; growth stated in official docs; raw block data from 20 sampled blocks × blocks per day (a lower bound, because state, receipts and indexes come on top). Pruned nodes and capped ledgers are shown as flat.
Bloat clock. Months until the disk is 90% full = (disk × 0.9 − data now) ÷ growth per month. It assumes today's growth rate; gas-limit increases and network upgrades can speed it up.
Cost. Cheapest configuration in our dated price list whose cores and RAM meet the official requirement and whose disk holds max(1.3 × today's data, 90% of the recommended disk). Bare metal fits any node; cloud/VPS plans with local disk fit non-validator nodes unless the docs ask for server-class hardware; a VPS plus network block storage only where the docs do not require local NVMe. EUR and USD plans are compared separately. Home build: the smallest listed mini PC with enough cores and RAM, plus one extra NVMe data drive if needed, at store list prices on the listed date, plus electricity at the stated assumption. Bandwidth is not priced.
Gas-limit scenario (Ethereum). Growth × (new gas limit ÷ today's gas limit). It assumes blocks stay as full as today and that disk growth scales with block gas; repricings such as EIP-8037 change the mix, so read it as a rough upper guide.
Sources: PublicNode snapshots; blockchain.com charts; litecoinspace.org; PublicNode JSON-RPC (block sampling); Official node documentation of each chain (linked per row); Provider price pages (linked in the price table)
Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.