Skip to content
HeroRPC

GUIDEIndex: Node hardware, 7 chapters

Blockchain node requirements: 24 chains, from their own docs

Blockchain node requirements range from a few cores and a few hundred gigabytes for Bitcoin-style chains to 16 cores, 256 GB of memory and several NVMe drives for Solana. We read the official operator docs of 24 chains and put CPU, memory, disk and network in one table, with the date each project gives.

Every row links the page the figures come from. Where the official docs are out of date, disagree or say nothing, the row says so instead of guessing.

Each chain has its own anchor, so you can link straight to it, and a link to the dedicated node we run for that chain.

Updated
Docs checked
Read
5 min

Where do you want to start?

In this guideThe quick answer

Quick answer

What hardware does a blockchain node need?

Bitcoin-style chains are the lightest: Zcash's Zebra asks for 4 cores, 16 GB of memory and 300 GB of disk.

Ethereum and EVM chains sit in the middle: Ethereum recommends 2+ / 4+ cores, 16 / 32 GB of memory and 2 / 4 TB NVMe; Arbitrum and BNB Chain want 64 GB of memory.

High-throughput chains are the heaviest: a Solana RPC node needs 16 cores / 32 threads+ and 256 GB+ (512 GB with all indexes) of memory, and Sui and TON ask for 128 GB.

  • Disk is NVMe almost everywhere
  • L2s also need an Ethereum RPC
  • Archive nodes need far more disk

CHAPTER 01

Bitcoin, Litecoin, Dogecoin, Zcash and Monero node requirements

The lightest nodes, and the thinnest official docs.

Bitcoin-style nodes need little CPU or memory; disk is the main cost. Their official docs are the thinnest in this index: bitcoin.org still lists 7 GB of disk, Litecoin's README says 22 GB, and Dogecoin and Monero give almost no hardware figures. Zebra, the Zcash node, is the exception.

Bitcoin-style chains: node hardware from official docs
ChainCPUMemoryDiskNetwork
BitcoinBitcoin CoreOut of datebitcoin.org and Bitcoin Core docs (undated)Hosted node, $139/moNot stated2 GB"Several hundred gigabytes or more"400 kbit/s up; about 200 GB up a month
LitecoinLitecoin CoreOut of dateLitecoin Core README (master, undated)Hosted node, $139/moNot statedNot statedAbout 22 GB (out of date)Not stated
DogecoinDogecoin CoreFew figuresDogecoin Core docs (master, undated)Hosted node, $139/moNot statedNot statedNot statedNot stated
ZcashZebra (zebrad)Zebra system requirements (undated)Hosted node, $139/mo2 / 4 cores4 / 16 GB300 GB100 Mbps, 300 GB a month
MoneromonerodFew figuresMonero docs (size as of 5 Oct 2026)Hosted node, $139/moNot statedNot statedAbout 105 GiB prunedNot stated
  • Bitcoin: bitcoin.org still lists 7 GB of free disk, which only fits a pruned node. The Core docs say several hundred GB.
  • Litecoin: The README's 22 GB is an old figure; the real chain is far larger. No CPU, memory or bandwidth figure.
  • Dogecoin: The official repo gives no runtime hardware figures, only 1.5 GB of memory for compiling.
  • Zcash: zcashd reached end of support on 18 July 2026; Zebra is the node to run.
  • Monero: Only the pruned size is published; pruning saves about two thirds of the disk.

CHAPTER 02

Ethereum, L2 and EVM node requirements

Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain and more.

EVM nodes mostly want 8 to 16 cores, 32 to 64 GB of memory and several terabytes of local NVMe. Layer 2 chains (Base, Arbitrum, Optimism, Starknet) also need an Ethereum RPC of their own to follow the main chain.

Ethereum and EVM chains: node hardware from official docs
ChainCPUMemoryDiskNetwork
EthereumExecution + consensus clientethereum.org, run a node (updated 17 Aug 2026)Hosted node, $139/mo2+ / 4+ cores16 / 32 GB2 / 4 TB NVMe25 / 50 Mbit/s down
Basebase/node with RethBase node performance (undated)Hosted node, $139/mo8+ cores32 / 64 GB2x chain + snapshot + 20%, local NVMeNot stated; plus an Ethereum RPC
ArbitrumNitroArbitrum node docs (Nitro v3.12.1)Hosted node, $139/mo8 / 16+ cores64 / 128 GB DDR5"Several TB", local NVMeNot stated; plus an Ethereum RPC
Optimismop-reth + op-nodeOut of dateOptimism node docs (sizes as of June 2025)Hosted node, $139/mo"Reasonably modern"16 GBAbout 700 GB (June 2025 figure)Not stated; plus an Ethereum RPC
LineaBesu + MaruFew figuresLinea, run a Besu node (updated 3 Nov 2025)Hosted node, $139/moNot statedNot statedAbout 509 GBNot stated
StarknetJunoJuno hardware requirements (Juno 0.16.0, 11 Sep 2026)Hosted node, $139/mo4 cores (8 for heavy RPC)8 GB (16 for heavy RPC)Fast NVMe, size not statedNot stated; plus an Ethereum RPC
PolygonBor + HeimdallDocs disagreePolygon prerequisites (undated)Hosted node, $219/mo8 / 16 cores32 / 64 GB4 / 6 TB1 Gbit/s
BNB Chainbsc (Geth fork)Out of dateBNB Chain node best practices (undated)Hosted node, $219/mo16 cores64 GB3 TB SSD5 MB/s
AvalancheAvalancheGoAvalanche system requirements (undated)Hosted node, $139/mo4 / 8+ cores16 / 32 GB1 / 2 TB local NVMe100 Mbps / 1 Gbps
Gnosis ChainNethermind, Erigon, Reth + consensus clientGnosis node docs (updated 6 Apr 2026)Hosted node, $139/mo4 threads16 GBNVMe preferred, size not statedUnmetered
Celoop-reth + op-nodeCelo, run a node (undated)Hosted node, $139/mo4 / 8 CPUs16 GB+1 TB+ (NVMe recommended)100 Mbit/s+ down
  • Base: Base gives a sizing formula instead of a disk number.
  • Optimism: The disk figure is from June 2025 and grows about 100 GB every six months.
  • Linea: Disk only; no CPU, memory or bandwidth figure.
  • Polygon: An older Polygon full-node page still says 4 cores and 16 GB, and the snapshot guide suggests an 8 TB disk.
  • BNB Chain: The README dates the 3 TB figure to December 2023.

Not sure whether you need a full or archive node? The archive node guide explains which queries need old state.

CHAPTER 03

Solana, Sui, Aptos, TON, Tron, XRP Ledger, Algorand and Cosmos

From light validators to the heaviest RPC nodes in crypto.

This group has the widest range: an Algorand validator runs on 8 vCPU and 16 GB, while Solana, Sui, Aptos and TON ask for 128 GB of memory or more and fast NVMe disks.

Other chains: node hardware from official docs
ChainCPUMemoryDiskNetwork
SolanaAgave, RPC nodeAnza requirements (undated)Hosted node, $579/mo16 cores / 32 threads+256 GB+ (512 GB with all indexes)NVMe: 1 TB accounts, 1 TB ledger, 500 GB snapshots1 Gbit/s unstaked; 2 Gbit/s+ staked
Suisui-nodeSui full node docs (undated)Hosted node, $289/mo8 cores (16 vCPU)128 GB4 TB NVMe (7 TB+ without pruning)Not stated
Aptosaptos-node, Validator specFew figuresAptos node requirements (undated)Hosted node, $289/mo48 threads128 GB3 TB enterprise NVMe, 60K IOPS1 Gbps
TONTON node (MyTonCtrl), LiteserverTON node setup (undated)Hosted node, $289/mo16 cores128 GB1 TB+ NVMe1 Gbps+; about 16 TB a month at peak
Tronjava-tronDocs disagreeTron install docs (updated 14 Oct 2026)Hosted node, $139/mo8 / 16 cores16 / 32 GB3 / 3.5 TB+ SSD100 Mbps
XRP LedgerxrpldXRPL system requirements (updated October 2026)Hosted node, $289/mo4+ / 8+ cores, 3 GHz+16 / 64 GB50 GB+ database, NVMe 10,000 IOPSGigabit
Algorandalgod, ValidatorAlgorand node types (undated)Hosted node, $139/mo8 vCPU16 GB100 GB NVMe1 Gbps, under 100 ms
Cosmos HubgaiadCosmos Hub, join mainnet (undated)Hosted node, $139/moNot stated16 GB2 TB (1 TB with default pruning)Not stated
  • Aptos: Aptos publishes one reference spec for validators and their fullnodes; it gives none for a public fullnode.
  • Tron: The java-tron README lists a 200 GB lite node and 5 Mbit/s as the minimum instead.
  • XRP Ledger: XRPL says its minimum is not enough to stay synced with Mainnet.

CHAPTER 04

Archive and validator node requirements

Where the docs give separate figures.

Archive nodes keep every past state, so they need far more disk: about 12 TB on Avalanche and TON, and 10 to 16 TB on BNB Chain and Polygon. Validators usually need the same or a little more than a full node, plus steady uptime.

Archive and validator nodes: hardware from official docs
ChainCPUMemoryDisk
EthereumArchiveOfficial docsAs full nodeAs full node2.2 TB+ (Reth) to 12 TB+ (Geth)
ArbitrumArchiveOfficial docs8 / 16+ cores64 / 128 GBAbout 3.7 TB snapshot
OptimismArchiveOfficial docsNot stated16 GBAbout 14 TB (June 2025)
LineaArchiveOfficial docsNot statedNot statedAbout 3.87 TB (Besu)
PolygonArchiveOfficial docs16 cores64 GB16 TB, 20k+ IOPS
BNB ChainArchiveOfficial docs16 cores128 GB10 TBBNB Chain's Erigon archive page says 64 GB and 5 TB instead.
AvalancheArchiveOfficial docsNot statedNot statedAbout 12.5 TB
TONArchiveOfficial docsNot statedNot statedAbout 12 TB
AlgorandArchiveOfficial docs8 vCPU16 GB3 TB SSD + 100 GB NVMe
SolanaValidatorOfficial docs12 cores / 24 threads+512 GB board suggestedNVMe: 1 TB accounts, 1 TB ledger, 500 GB snapshotsStaked validators need 2 Gbit/s or more; 10 Gbit/s recommended.
SuiValidatorOfficial docs24 cores (48 vCPU)128 GB4 TB NVMe
TronSuper RepresentativeOfficial docs32 cores64 GB3.5 TB+ SSD
Cosmos HubValidatorOfficial docsNot stated32 GB500 GB to 2 TB, by pruning

CHAPTER 05

Where the official docs are out of date or silent

Read every figure with its date.

In 4 of 24 chains, the official figure is plainly out of date; in 2, two official pages disagree; and in 4, the docs leave out most figures. Use the newest dated page, and size your disk for growth, not for today.

  • Out of date: bitcoin.org's 7 GB, Litecoin's 22 GB, Optimism's June 2025 sizes and BNB Chain's December 2023 disk figure.
  • Disagreeing: Polygon's two hardware pages, BNB Chain's two archive pages, and Tron's docs against its README.
  • Silent: Dogecoin and Monero give almost no hardware figures; Linea gives disk only; Aptos gives none for a public fullnode.

CHAPTER 06

How to size a node server

Disk speed first, then memory, then cores.

Pick local NVMe over network disks, buy memory at the recommended figure rather than the minimum, and leave room for a year of chain growth. For L2s, budget for an Ethereum RPC as well.

Before you buy the server

0 of 6 done

CHAPTER 07

Skip the hardware: dedicated nodes on HeroRPC

Every chain in this index, on its own server.

HeroRPC runs a dedicated node for every chain in this index, from $139 a month. Each row above links that chain's node page with its exact price.

See every chain and node type on node pricing, or work out what running one yourself costs in the Ethereum node cost guide.

QUESTIONS

Node requirements questions

What are the hardware requirements for an Ethereum node?

ethereum.org recommends 2+ / 4+ cores, 16 / 32 GB of memory and 2 / 4 TB NVMe, with 50 Mbit/s down. The minimum is 2 cores, 16 GB and a 2 TB NVMe disk.

What are the Polygon node requirements?

Polygon's prerequisites page lists 8 / 16 cores, 32 / 64 GB of memory and 4 / 6 TB and 1 Gbit/s for a full node, as minimum and recommended. An older Polygon page gives lower figures, and the snapshot guide suggests an 8 TB disk.

What are the Solana node requirements?

Anza's docs ask for 16 cores / 32 threads+, 256 GB+ (512 GB with all indexes) of memory and separate NVMe disks for accounts and ledger for an RPC node. Validators need 12 cores / 24 threads or more and at least 2 Gbit/s if staked.

What are the Bitcoin node requirements?

Bitcoin's docs list 2 GB of memory and an upload of at least 400 kbit/s, and say the full chain needs several hundred gigabytes. bitcoin.org's 7 GB disk figure only fits a pruned node.

What are the Arbitrum node requirements?

Arbitrum's docs ask for 8 / 16+ cores, 64 / 128 GB DDR5 of memory and several terabytes of local NVMe, plus an Ethereum RPC and beacon endpoint.

What are the Tron node requirements?

Tron's docs list 8 / 16 cores, 16 / 32 GB of memory and 3 / 3.5 TB+ SSD and 100 Mbps. A block-producing Super Representative needs 32 cores and 64 GB.

ABOUT

How we made this guide

In October 2026 we read the official operator docs or repositories of all 24 chains, and only those. Each row shows the date or version the page gives, or "undated". Where a page gave minimum and recommended figures we show both. Unclear tables were re-read on the live page. We did not benchmark the chains ourselves.

Written by

HeroRPC team

Written and checked by the people who run HeroRPC's builder and node servers. Every figure links to its source.

Published . Last updated .

Get the node without the hardware

A dedicated node for any chain in this index, from $139 a month. Pay in crypto; ready within 24 hours.