> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/mezo-org/documentation/llms.txt
> Use this file to discover all available pages before exploring further.

# Active Validators

> Information about Mezo Validators and how to participate in network security

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 Name   | Status  | Website                                                    |
| ---------------- | ------- | ---------------------------------------------------------- |
| Animoca          | Running | [animocabrands.com](https://www.animocabrands.com/)        |
| aras.haus        | Running | [aras.haus](https://www.aras.haus/)                        |
| Beemeeupnow      | Running | [@beemeeupnow](https://x.com/beemeeupnow)                  |
| Boar             | Running | [github.com/boar-network](https://github.com/boar-network) |
| Chorus One       | Running | [chorus.one](https://chorus.one/)                          |
| ChainDAQ         | Running | [chaindaq.com](https://www.chaindaq.com/)                  |
| Encode           | Running | [encode.club](https://www.encode.club/)                    |
| Enigma           | Running | [enigma-validator.com](https://enigma-validator.com/)      |
| Flowdesk         | Running | [flowdesk.co](https://flowdesk.co/)                        |
| GlobalStake      | Running | [globalstake.io](https://globalstake.io/)                  |
| Imperator        | Running | [imperator.co](https://www.imperator.co/)                  |
| InfraSingularity | Running | [infrasingularity.com](https://infrasingularity.com/)      |
| Lavender.Five    | Running | [lavenderfive.com](https://www.lavenderfive.com/)          |
| Liquid Lambda    | Running | [liquidlambda.com](https://www.liquidlambda.com/)          |
| Maestro          | Running | [gomaestro.org](https://www.gomaestro.org/)                |
| Node.Monster     | Running | [node.monster](https://www.node.monster/)                  |
| P2P              | Running | [p2p.org](https://www.p2p.org/)                            |
| SenseiNode       | Running | [senseinode.com](https://www.senseinode.com/)              |
| Simply Staking   | Running | [simplystaking.com](https://simplystaking.com/)            |
| StakingCabin     | Running | [stakingcabin.com](https://www.stakingcabin.com/)          |
| Validation Cloud | Running | [validationcloud.io](https://www.validationcloud.io/)      |

## Becoming a Validator

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

<Steps>
  <Step title="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](/nodes/validator-kit#hardware-requirements) for detailed specifications.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Setup Validator Node">
    Once approved, follow the [Validator Kit](/nodes/validator-kit) guide to set up and configure your validator node.
  </Step>

  <Step title="Join the Network">
    Complete the validator setup process and begin participating in consensus.
  </Step>
</Steps>

<Note>
  Mezo uses a Proof of Authority consensus mechanism. All validators must be approved before they can participate in network consensus.
</Note>

## 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

<Warning>
  Validators must maintain high uptime and follow security best practices. Failure to do so may result in removal from the validator set.
</Warning>

## Next Steps

<CardGroup cols={2}>
  <Card title="Validator Kit" icon="toolbox" href="/developers/nodes/validator-kit">
    Learn how to set up your validator node
  </Card>

  <Card title="Node Overview" icon="server" href="/developers/nodes/overview">
    Understand different node types
  </Card>
</CardGroup>