> For the complete documentation index, see [llms.txt](https://meta-earth.gitbook.io/white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meta-earth.gitbook.io/white-paper/tokenomics/mec.md).
# MEC
MEC is the native token of Meta Earth, with a total supply of 20 billion tokens. Out of these, 10 billion tokens are permanently locked within the network, while the remaining 10 billion tokens are released through a mechanism that halves the supply annually. This rule will be encoded into the genesis block.
* The initial 10 billion MEC tokens are permanently locked through staking, roughly equivalent to the world's total population, ensuring that each individual has a corresponding MEC token. These tokens cannot be unstaked, traded, or spent.
* The other 10 billion MEC tokens are generated exclusively through staking MEC.
Upon the launch of the ME Network mainnet, this rule will officially take effect. According to the encoding rules, the total circulating supply of MEC in the entire network is 10 billion tokens. In the first year, 5 billion tokens will be released. The earlier a user obtains an ME ID, the more MEC they can acquire. For users without an ME ID, the corresponding released MEC will be allocated to Meta Earth’s Global Network Treasury.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://meta-earth.gitbook.io/white-paper/tokenomics/mec.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.