FlameWireDocs

Hardware Requirements

This guide details the hardware specifications needed to run full-archive nodes for supported chains on FlameWire.

Current Recommendations

These specifications are current as of Q1 2026. Storage requirements grow over time as blockchains accumulate more data.

Bittensor — Archive Node

ComponentSpecification
CPU8 vCPU
RAM32 GB
Storage4 TB NVMe SSD
Bandwidth500 Mbps

Note: Runs performance scoring and gossip; modest disk but steady network traffic.

Ethereum — Geth (gcmode=archive) (coming soon)

ComponentSpecification
CPU16 vCPU
RAM64 GB
Storage8 TB NVMe SSD
Bandwidth1 Gbps

Note: Highest disk I/O and RAM footprint; needed if you must serve every legacy debug trace.

Ethereum — Erigon Archive (coming soon)

ComponentSpecification
CPU8 vCPU (12 vCPU ideal)
RAM32 GB
Storage4 TB NVMe SSD
Bandwidth1 Gbps

Note: Table-oriented storage is approximately 50% smaller than Geth; good balance of speed and cost.

Sui — Full Node (coming soon)

ComponentSpecification
CPU16 vCPU
RAM128 GB
Storage4 TB NVMe SSD
Bandwidth500 Mbps

Note: Indexer doubles IOPS; NVMe essential for checkpoint queries.

General Guidelines

NVMe Required

All drives must be NVMe with latency under 100 µs and ≥100k IOPS. SATA SSDs will bottleneck archive reads.
  • Prefer bare-metal or dedicated cloud instances to avoid I/O contention
  • Consider RAID 0 striping of two NVMe drives for Ethereum syncing
  • Plan storage growth: Ethereum ~0.5 TB/year; Sui ~0.2 TB/year
  • 1 Gbps provides comfortable headroom; bandwidth-constrained regions should limit RPC concurrency