> For the complete documentation index, see [llms.txt](https://docs.memecore.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.memecore.com/guides/consensus/validator.md).

# Validator

### | Overview <a href="#or-overview" id="or-overview"></a>

MemeCore Chain operates with a network of validators using a Proof of Meme (PoM) consensus mechanism, designed to enable short block times and reduced transaction fees. Validators with the highest staked amounts have the chance to produce blocks. Security, stability, and finality are maintained through slashing mechanisms like double-sign detection.

The chain uses a real-time election process to select the top 7 active validators for block production, based on staking rankings. This validator list is refreshed every 10 blocks, or approximately every 70 seconds. To qualify as a candidate for election, validators must first stake a set amount of assets into the system contract.

### | What are Validators? <a href="#or-what-are-validators" id="or-what-are-validators"></a>

Validators on the MemeCore network play a key role in maintaining security and producing blocks using the PoM consensus mechanism. These nodes handle transaction packaging and block validation, ensuring the stability of the network. In return for their efforts, validators earn $M tokens as rewards for their contribution to securing the system.

### | Economics <a href="#or-economics" id="or-economics"></a>

Validators and delegators earn two types of rewards: $M tokens and ERC-20 tokens. For instance, if the reward for producing a block is 1,000 $M, these tokens aren’t given directly to the block proposer. Instead, they are distributed proportionally among validators and delegators based on their respective stakes in the network.

Example:

Copy

```
M staker shares: 1,000 * 75% = 750 M
Meme coin staker shares: 1,000 * 24% = 240 M
Block producer shares: 1,000 * 1% = 10 M

The M staker commission rate is: 10%
The meme coin staker commission rate is: 15%

Validator rewards: (his staking reward in $M and ERC-20) + ($M and ERC-20 commission) + (10 $M for the block producer)
Delegators get: (his staking reward in $M and ERC-20) - ($M and ERC-20 commission)
```

### | Running a Validator Node <a href="#or-running-a-validator-node" id="or-running-a-validator-node"></a>

**Hardware Requirements**

The following are the minimum hardware requirements:

* CPU with 2+ cores
* 4GB RAM
* 200GB free storage space
* 8 MBit/sec download Internet service

### | Validator Management Contract Address <a href="#or-validator-management-contract-address" id="or-validator-management-contract-address"></a>

Validator management contract:`0x1234000000000000000000000000000000000002`

### | $M Staking <a href="#or-usdm-staking" id="or-usdm-staking"></a>

Send at least 7,000,000 $M from your miner address to the `register` method of the validator contract without any parameters. The staked $M will be fully refunded when quit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.memecore.com/guides/consensus/validator.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.