Open explorer ↗
Ecrox Chain / Validators

Secure Ecrox Chain. Earn rewards.

Validators run the DPoS consensus layer: they produce blocks, keep the chain in sync and are backed by ECROX delegated from the community.

Ways to take part

Choose a role that matches your hardware, stake and how much responsibility you want.

Consensus

Active validator

Produce and sign blocks as part of the active validator set. Needs dedicated server infrastructure, high uptime and a bonded ECROX stake.

Standby

Candidate validator

Run a synced validator node and gather delegations. Candidates move into the active set as delegated stake grows.

Community

Delegator

No server needed. Delegate ECROX to a validator you trust and share in its rewards.

Onboarding

Bring a validator online in a controlled sequence.

Step 1

Get ECROX

Hold the required stake in a self-custody wallet. Never share private keys or seed phrases.

Step 2

Provision servers

Use reliable bare-metal or cloud servers with fast SSD storage, stable networking, monitoring and time sync.

Step 3

Install and sync

Install the Ecrox node software, sync the full chain and configure peers, validator keys and telemetry.

Step 4

Register and bond

Register your validator, bond your stake and confirm block signing on the explorer.

Production checklist

Uptime and key security decide how a validator performs.

Server

Compute and storage

Fast NVMe storage with headroom for chain growth, enough RAM for state and room to scale IOPS.

Network

Connectivity

Redundant, high-bandwidth connections, firewall rules and private management access.

Security

Key handling

Separate validator keys from public RPC, keep encrypted backups and limit who has access.

Operations

Monitoring

Alert on missed blocks, peers, disk, CPU and memory, and test your recovery plan before upgrades.

Current requirements: Minimum stake, hardware specs and validator-set size are set by the protocol and can change. Check the latest values in the Ecrox documentation before you provision servers.