This page will be expanded as mainnet launch approaches. Hardware and configuration specifics are marked TBD; values will harden once load testing and the genesis process are complete. Pre-mainnet the validator set is operated by the foundation and invited partners.
Hardware requirements (TBD)
Intention is a high-throughput L1 with protocol-native matching, so validator hardware is closer to an HFT co-location box than a typical chain node.| Resource | Minimum | Recommended | Notes |
|---|---|---|---|
| CPU | TBD | TBD | Modern multi-core with AVX2, dedicated cores for the engine |
| Memory | TBD | TBD | Headroom for the order book state |
| Storage | TBD NVMe | TBD NVMe | Low-latency SSD; HDDs are not supported |
| Network | 1 Gbps | 10 Gbps | Stable, low-jitter; geographically diverse peering |
Software install (placeholder)
The validator binary, release channels, and container images will be published with the mainnet launch package. Expect a single binary plus a systemd unit file, and a container image for operators running on orchestrated infrastructure.Provision the host
Install a supported Linux distribution, disable swap, tune
ulimit -n, and apply the standard kernel parameters for low-latency networking.Generate validator keys
Run the key-generation tool to produce a consensus key and a node identity key. Back up both to offline media. Consensus keys must live in an HSM or at minimum a hardware-backed keystore.
Configure the node
Fill in the config template: chain ID, bootstrap peers, external address, log level, metrics endpoint, and the keystore paths. Set Prometheus scrape, JSON log output, and alert webhooks.
Join the validator set
Submit the validator registration transaction with your node identity, contact endpoint, and operator metadata. Pre-mainnet this step is coordinated with the foundation; on mainnet it goes through the standard join flow.
Configuration surface
A validator config covers identity (keys, endpoints), networking (listen addresses, peer limits), consensus parameters (propose timeouts, batch sizes — set at protocol level, overridable only within a narrow band), the engine (worker pool, queue caps), and observability (Prometheus, tracing, logs).Day-two operations
Monitoring
Dashboards, alert thresholds, and the four-layer metric pyramid.
DDoS and Sybil defense
Rate limiting, connection control, and congestion fair-share at the network edge.
For where validators sit in the network — sequencers, full nodes, public RPC — see Network topology.