Skip to Content
OperateGetting startedHardware requirements

Hardware requirements

Data availability nodes

Non-archival data availability nodes

Node typeMemoryCPUDiskBandwidth
Light node500 MB RAMSingle core20 GB SSD56 Kbps
Bridge node64 GB RAM32 cores25 TiB NVME1 Gbps

Non-archival disk recommendations use a 7-day planning window sized for the 128MB/6s maximum-throughput envelope, which provides headroom above the current maximum block capacity of 32 MiB at approximately 3-second blocks. These are conservative recommendations; operators may provision less by pruning more aggressively at their own risk.

Bridge nodes run in pruned mode by default.

Archival data availability nodes

Node typeMemoryCPUDiskBandwidth
Light node (unpruned headers)500 MB RAMSingle core7 TiB NVME*56 Kbps
Bridge node (--archival)64 GB RAM32 cores637 TiB NVME*1 Gbps

*Archival disk recommendations use a 1-year planning window sized for the 128MB/6s maximum-throughput envelope, which provides headroom above the current maximum block capacity of 32 MiB at approximately 3-second blocks. Actual usage can be much lower. Regularly check disk usage and maintain at least 1 month of maximum-throughput capacity as additional free space.

To run an archival bridge node, start with a fresh store and pass --archival every time you run celestia bridge start. A store previously started in pruned mode cannot switch to archival mode.

Consensus nodes

Non-archival consensus nodes

Node typeMemoryCPUDiskBandwidth
Validator32 GB RAM32 cores12 TiB NVME1 Gbps
Consensus node32 GB RAM32 cores12 TiB NVME1 Gbps

Non-archival disk recommendations use a 7-day planning window sized for the 128MB/6s maximum-throughput envelope, which provides headroom above the current maximum block capacity of 32 MiB at approximately 3-second blocks. These are conservative recommendations; operators may provision less by pruning more aggressively at their own risk.

Archival consensus nodes

Node typeMemoryCPUDiskBandwidth
Consensus node64 GB RAM32 cores624 TiB NVME*1 Gbps

*Archival disk recommendations use a 1-year planning window sized for the 128MB/6s maximum-throughput envelope, which provides headroom above the current maximum block capacity of 32 MiB at approximately 3-second blocks. Actual usage can be much lower. Regularly check disk usage and maintain at least 1 month of maximum-throughput capacity as additional free space.

Validators must use hardware that passes the CPU benchmark . If your server does not pass, upgrade to a more powerful machine.

For a list of CPUs tested against the v6 128MB/6s workload, see the release notes . Other CPUs are acceptable if they pass the benchmark. Recommended CPU specs:

  • 32 or more cores
  • GFNI (Galois Field New Instructions) support
  • SHA-NI (SHA New Instructions) support

Feel stuck? Go to our Discord!

Last updated on