Skip to main content
Mezo operates on a Proof of Authority (PoA) consensus mechanism, where approved validators are responsible for securing the network, verifying transactions, and producing blocks.

Current Network Validators

The following validators are currently running on the Mezo network:
Validator NameStatusWebsite
AnimocaRunninganimocabrands.com
aras.hausRunningaras.haus
BeemeeupnowRunning@beemeeupnow
BoarRunninggithub.com/boar-network
Chorus OneRunningchorus.one
ChainDAQRunningchaindaq.com
EncodeRunningencode.club
EnigmaRunningenigma-validator.com
FlowdeskRunningflowdesk.co
GlobalStakeRunningglobalstake.io
ImperatorRunningimperator.co
InfraSingularityRunninginfrasingularity.com
Lavender.FiveRunninglavenderfive.com
Liquid LambdaRunningliquidlambda.com
MaestroRunninggomaestro.org
Node.MonsterRunningnode.monster
P2PRunningp2p.org
SenseiNodeRunningsenseinode.com
Simply StakingRunningsimplystaking.com
StakingCabinRunningstakingcabin.com
Validation CloudRunningvalidationcloud.io

Becoming a Validator

To become a validator on the Mezo network, you must:
1

Meet Technical Requirements

Ensure you have the necessary hardware and infrastructure:
  • CPU: 8 cores (recommended)
  • RAM: 16GB (recommended)
  • Storage: 500GB NVMe SSD (recommended)
  • Network: 1 Gbps (recommended)
See hardware requirements for detailed specifications.
2

Apply for Proof of Authority

Submit an application for Proof of Authority (PoA) status through the official Mezo channels. The PoA process ensures that validators are trusted entities committed to network security.
3

Setup Validator Node

Once approved, follow the Validator Kit guide to set up and configure your validator node.
4

Join the Network

Complete the validator setup process and begin participating in consensus.
Mezo uses a Proof of Authority consensus mechanism. All validators must be approved before they can participate in network consensus.

Validator Responsibilities

Validators play a critical role in the Mezo network and are responsible for:
  • Block Production: Proposing new blocks to the blockchain
  • Transaction Verification: Validating transactions before inclusion in blocks
  • Consensus Participation: Attesting to proposed blocks and participating in the consensus mechanism
  • Network Security: Maintaining high uptime and security standards
  • Infrastructure Maintenance: Keeping nodes updated and properly configured

Validator Requirements

Technical Requirements

  • Dedicated hardware or cloud infrastructure meeting minimum specifications
  • Reliable network connectivity with low latency
  • 24/7 uptime and monitoring
  • Regular software updates and maintenance

Operational Requirements

  • Active participation in network governance (if applicable)
  • Responsive to security updates and critical patches
  • Proper key management and security practices
  • Backup and disaster recovery procedures
Validators must maintain high uptime and follow security best practices. Failure to do so may result in removal from the validator set.

Next Steps

Validator Kit

Learn how to set up your validator node

Node Overview

Understand different node types

Build docs developers (and LLMs) love