> For the complete documentation index, see [llms.txt](https://service.block-pro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://service.block-pro.net/mainnet/celestia/requirements.md).

# Requirements

**Mainnet** · Chain ID `celestia`

Use Ubuntu 24.04 LTS on x86\_64 for these guides. Linux celestia-app multiplexer binaries require glibc 2.38 or newer.

## Hardware

These are current **Mainnet starting points**, not a guarantee of retention or future capacity.

| Node profile                      | CPU      | RAM    | Disk       | Network |
| --------------------------------- | -------- | ------ | ---------- | ------- |
| Light, pruned                     | 1 core   | 500 MB | 20 GB SSD  | 56 Kbps |
| Bridge, pruned                    | 32 cores | 64 GB  | 2 TB NVMe  | 1 Gbps  |
| Consensus, pruned                 | 32 cores | 32 GB  | 2 TB NVMe  | 1 Gbps  |
| Validator, base consensus process | 32 cores | 32 GB  | 2 TB NVMe  | 1 Gbps  |
| Bridge, archival                  | 32 cores | 64 GB  | 12 TB NVMe | 1 Gbps  |
| Consensus, archival               | 32 cores | 64 GB  | 16 TB NVMe | 1 Gbps  |

Storage depends on traffic, pruning and history. Leave working space for compaction and snapshot restoration. Size the consensus process separately when it shares a server with a bridge. Validators must pass Celestia's CPU benchmark. Fibre needs additional memory and a separate data disk; it is not included in the validator row.

Source: [Hardware requirements](https://docs.celestia.org/operate/getting-started/hardware-requirements/).

## Fibre capacity

Fibre runs alongside the validator role on a separate server. Allow at least **32 GB RAM** and pass the [official CPU benchmark](https://github.com/celestiaorg/celestia-app/blob/main/tools/cpu_requirements/README.md). With the default connection limits, receive buffers alone can approach **27 GiB**, so leave additional headroom for the service and OS.

Use the Mainnet tab in the [Fibre capacity calculator](https://docs.google.com/spreadsheets/d/1P3k-KQrZxbRjRwIxWkJBNwgAFlFMJUdT7OupA_WoKa0/edit?gid=971673838#gid=971673838) for disk and ingress sizing based on your current stake. Launch values and possible future throughput scenarios are separate. Add download capacity and local metadata storage. Keep Fibre data on a different disk from consensus data.

Place Fibre, the validator and any object-storage bucket in the same datacenter or region. Remote signing requires mTLS; an external KMS must support SignRawBytes and meet the signing-latency requirement. See [Fibre](/mainnet/celestia/validator-node/fibre.md) for the complete setup.

## Ports

| Port             | Purpose                | Exposure                                     |
| ---------------- | ---------------------- | -------------------------------------------- |
| 26656 TCP        | Consensus P2P          | Public when accepting peers                  |
| 2121 TCP and UDP | DA P2P                 | Public for bridge connectivity               |
| 26657 TCP        | Consensus HTTP RPC     | Local by default                             |
| 9090 TCP         | Application gRPC       | Local or private by default                  |
| 9098 TCP         | Core gRPC listener     | Local or private by default                  |
| 26669 TCP        | Validator signing gRPC | Fibre host only; mTLS for remote connections |
| 7980 TCP         | Fibre client traffic   | Public on the Fibre host                     |
| 26658 TCP        | DA node JSON-RPC       | Local and authenticated                      |

Your reverse proxy can expose public endpoints on a different port. Port 443 does not itself prove that a gRPC service supports TLS.

Source: [Consensus installation](https://docs.celestia.org/operate/consensus-validators/install-celestia-app/) and [bridge setup](https://docs.celestia.org/operate/data-availability/bridge-node/).