Monday, November 16, 2026

A Polygon PoS node holds 115 GB today; even 16 TB lasts under two years

A Polygon PoS node runs Bor (execution) and Heimdall (consensus). The official spec asks for 4–6 TB of disk even though pruned snapshots are small.

Updated 3.7 h ago

A 4 TB disk cannot be timed yet

Pruned node (Bor pruned + Heimdall)

This is a pruned node, not a full node: PublicNode's Bor pruned snapshot (~112 GB) plus Heimdall (~11 GB). It keeps only recent state, which is why it is so much smaller than the 4 TB the docs ask for a full node. Growth appears once we have 10 days of snapshot history.

Official requirements

CPU
8 cores (16 recommended)
RAM
32 GB
Disk
4 TB (6 TB recommended) for a full node; Polygon publishes no separate figure for a pruned node
Bandwidth
1 Gbit/s
Source
Polygon docs: prerequisites (undated, checked 2026-11-12)

Data and growth

Data now
115 GB Measured
PublicNode snapshot (bor 2.11.0-priv, 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: 11 points since 12 Nov 2026

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 AX102 (16 cores, 128 GB DDR5 ECC, 2 × 1.92 TB NVMe) at from €159/month, price page (2026-11-12)

Home build: about $2,115 one-off (Minisforum UM890 Pro (Ryzen 9 8945HS, 8 cores, 32 GB, 1 TB SSD) $1,015 + Samsung 990 PRO 4 TB $1,100; store list prices, 12 Nov 2026) plus about €6.35/month in electricity.

Full node (Bor + Heimdall)

Measured size is PublicNode's full (unpruned) Bor snapshot, base plus incremental parts, about 7.5 TB: well above the 4–6 TB in Polygon's docs, which look out of date. Heimdall adds about 11 GB.

Official requirements

CPU
8 cores (16 recommended)
RAM
32 GB
Disk
4 TB (6 TB recommended)
Bandwidth
1 Gbit/s
Source
Polygon docs: prerequisites (undated, checked 2026-11-12)

Data and growth

Data now
7.48 TB Measured
PublicNode snapshot (bor 2.11.1-priv, uncompressed, base + incremental parts), 15 Nov 2026
Growth
at least +171 GB/mo Lower bound
Raw block data only: about 97,341 bytes per block × 57,600 blocks a day (median of recent samples). State, receipts and indexes come on top, so real disk growth is higher. Source: PublicNode RPC, 30 sampled blocks per run

Snapshot size history: 5 points since 12 Nov 2026

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

1 TBToo small
2 TBToo small
4 TBToo small
8 TBToo small

What it costs

Server: none of the plans in our price list has enough RAM, cores or NVMe for this node (9.73 TB needed). Expect custom bare metal.

Home build: not realistic for this node (needs more cores, RAM or disk than a mini PC holds).

Archive node (Erigon)

Official requirements

CPU
16 cores
RAM
64 GB
Disk
16 TB (io1, 20k+ IOPS, RAID-0)
Bandwidth
1 Gbit/s
Source
Polygon docs: prerequisites (undated, checked 2026-11-12)

Data and growth

Data now
13.26 TB Measured
PublicNode snapshot (bor 2.11.0-priv, uncompressed, base + incremental parts), 12 Nov 2026
Growth
at least +171 GB/mo Lower bound
Raw block data only: about 97,341 bytes per block × 57,600 blocks a day (median of recent samples). State, receipts and indexes come on top, so real disk growth is higher. Source: PublicNode RPC, 30 sampled blocks per run

Snapshot size history: 3 points since 10 Nov 2026

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

1 TBToo small
2 TBToo small
4 TBToo small
8 TBToo small

What it costs

Server: none of the plans in our price list has enough RAM, cores or NVMe for this node (17.24 TB needed). Expect custom bare metal.

Home build: not realistic for this node (needs more cores, RAM or disk than a mini PC holds).

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

Also on the Network Desk for Polygon

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.