PerformanceBlog
Tempo MCP serverGive agents search and read tools for Tempo docs
Skip to content
LogoLogo

System Requirements

These are the minimum and recommended system requirements for running a validator/RPC node. It is likely, that the nodes will not require as much resources at the beginning of the chain, but we still highly recommend to follow the recommended specifications. This will allow for future growth and scalability.

Consensus state can live on a lower performance volume (for example, EBS), but execution state needs NVMe storage. If you want to separate them, use --datadir for execution data and --consensus.datadir for consensus data.

RPC Node

ComponentMinimumRecommended
CPU16 cores32+ cores
RAM32 GB64 GB
Storage1000 GB NVMe2000 GB NVMe
Network1 Gbps10 Gbps

Validator Node

ComponentMinimumRecommended
CPU8 cores16+ cores
RAM16 GB32 GB
Storage100 GB NVMe1 TB NVMe
Network1 Gbps1 Gbps

Cloud provider recommendations

These dedicated servers meet or exceed the recommended specs for both RPC and validator nodes:

ProviderServerCPURAMStorage
OVHAdvance-4Intel Xeon-E 2386G (6c/12t)32 GB2× 512 GB NVMe
HetznerAX42AMD Ryzen 5 3600 (6c/12t)64 GB2× 512 GB NVMe
AWSc6id.8xlarge32 vCPUs64 GB1.9 TB NVMe

Time Synchronization

Tempo validates that block timestamps are not in the future. If your system clock drifts even slightly, your node may reject valid blocks or produce blocks that other validators reject — leading to consensus errors and missed proposals.

sudo apt install chrony
sudo systemctl enable --now chronyd

Verify synchronization

chronyc tracking

Check that System time offset is under a few milliseconds and Leap status is Normal. You can also verify with:

timedatectl

Confirm System clock synchronized: yes and NTP service: active.

Cloud providers

Most cloud providers (AWS, Hetzner, OVH) pre-configure NTP, but minimal VM images may ship without a proper NTP daemon. Always verify that chrony or ntpd is installed and running after provisioning a new machine.

Security

For network configuration, key management, release verification, and other security best practices, see the dedicated Node Security page.

Network Tuning

We recommend enabling TCP BBR congestion control with the fq packet scheduler for better P2P and consensus performance.

Add the following to your sysctl configuration (e.g. /etc/sysctl.d/99-tempo-network.conf or equivalent):

net.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = bbr

Apply and verify:

sudo sysctl --system
sysctl net.ipv4.tcp_congestion_control   # should print: bbr
sysctl net.core.default_qdisc            # should print: fq

Restart the node after applying for the changes to take effect.

Ports

PortProtocolPurposeExpose
30303TCP/UDPExecution P2PPublic
8000TCPConsensus P2PValidators only
8545TCPHTTP RPCOptional (internal for validators)
8546TCPWebSocket RPCOptional (internal for validators)
9000TCPMetricsInternal