Types of Nodes

Nexera is a Proof-of-Stake (PoS) network that utilizes the Ethereum Virtual Machine (EVM). $NXRA, the native token of the network, is currently used to pay for transaction gas fees. While staking is not enabled at this time, it may be introduced in future network upgrades.

This document specifies the technical requirements for operating a node on the Nexera Network.

Note

All Nexera Network nodes use a dual-client architecture: RETH as the Execution Client for transaction processing and EVM state, and Lighthouse as the Consensus Client for managing block validation and finality. Known for high performance and low resource usage, this combination enables scalable, efficient, and resilient node infrastructure.

Full Node

A full Nexera node requires two software clients running concurrently: an Execution Client (EC) and a Consensus Client (CC). The EC is responsible for EVM state and transaction execution, while the CC manages the Proof-of-Stake consensus protocol.

Execution Client (EC)

The recommended client for the Execution Node is RETH. The EC's primary functions are to process transactions within the EVM, maintain the network's state, and provide a JSON-RPC API for applications to interact with the blockchain. It validates new blocks received from the Consensus Node by re-executing the transactions contained within them.

System Requirements

ComponentRequirements
CPU4+ cores with a base speed of 3.5-4.0 Ghz
RAM16+ GB
SSD2+ TB (TLC recommended; avoid QLC)
Network≥ 25 Mbps Symmetric
SystemUbuntu Server 22.04 LTS

Consensus Client (CC)

The required client for the Consensus Node is Lighthouse. The CC manages network consensus by following the head of the beacon chain and validating blocks and attestations. When configured with validator keys, it also handles block proposals and attestations. Transaction finality is achieved when a block is attested to by a 2/3 supermajority of the validator set.

System Requirements

ComponentRequirements
CPU2-4 cores with a base speed of 3.5-4.0 Ghz
RAM8+ GB
SSD~200 GB (TLC recommended; avoid QLC)
Network≥ 25 Mbps Symmetric
SystemUbuntu Server 22.04 LTS

Combined System Requirements

ComponentRequirements
CPU≥ 4 cores ≥ 3.5-4.0 GHz base clock speed
RAM≥ 32 GB
SSD≥ 2 TB NVMe SSD (TLC recommended; avoid QLC)
Network≥ 100 Mbps download, ≥ 20 Mbps upload
SystemUbuntu Server 22.04 LTS

Validator Node

Currently, the validator role is not available for public use because the network is in the development phase.

Archive Node

An archive node is a specialized type of full node that stores the complete history of the blockchain, from the very first block (the "genesis block") to the most recent one. While a standard full node keeps all block data, it periodically "prunes" historical states to save disk space, only retaining enough data to validate the chain and serve recent requests.

An archive node, in contrast, forgoes this pruning, creating a complete historical index of every state the blockchain has ever been in.

System Requirements

ComponentRequirements
CPU8–16 cores, ≥3.5 GHz base clock speed
RAM32–64 GB
SSD≥3 TB NVMe SSD (TLC recommended; avoid QLC)
Network≥100 Mbps download, ≥20 Mbps upload
SystemUbuntu Server 22.04 LTS

Light Node

A light node is a client that stores only block headers and requests necessary data from full nodes. It validates transactions using simplified payment verification (SPV), requiring significantly less storage and computational resources. While it cannot participate in consensus or validate the entire blockchain state, it enables lightweight applications and wallet services to interact with the Nexera network efficiently.

ComponentRequirements
CPU4 cores, ≥3.5 GHz base clock speed
RAM16 GB
SSD256 GB SSD (TLC recommended; avoid QLC)
Network≥100 Mbps download, ≥20 Mbps upload
SystemUbuntu Server 22.04 LTS

On this page