Monday, November 16, 2026

A Zcash node holds 300 GB today; even 16 TB lasts under two years

Zebra, the Zcash Foundation's node, runs on modest hardware with about 300 GB of state.

Updated 3.7 h ago

A 4 TB disk cannot be timed yet

Full node (Zebra)

NU7 (5 Nov 2026) cut block time to 25 s, so blocks arrive 3× faster; we have no growth figure since then.

Official requirements

CPU
2 cores min, 4 recommended
RAM
16 GB
Disk
300 GB (state about 300 GB; restoring a snapshot needs about twice that)
Bandwidth
100 Mbit/s, about 300 GB/month
Source
Zebra book: requirements (undated, checked 2026-11-12)

Data and growth

Data now
300 GB Documented
Zebra book, 12 Nov 2026
Growth
— No data
No published or measurable growth figure

Bloat clock (disk 90% full at today's growth)

1 TBNo data yet
2 TBNo data yet
4 TBNo data yet
8 TBNo data yet

What it costs

Server: Hetzner AX41-NVMe (6 cores, 64 GB, 2 × 512 GB NVMe) at €59.00/month, price page (2026-11-12)
In USD: DigitalOcean Basic 16 GB + 70 GB volume $103/month

Home build: about $389 one-off (Beelink EQ14 (Intel N150, 4 cores, 16 GB, 500 GB SSD) $389; store list prices, 12 Nov 2026) plus about €6.35/month in electricity.

Running this node? See also: latest client releases (Node Patch Radar).

Also on the Network Desk for Zcash

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.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.