> For the complete documentation index, see [llms.txt](https://docs.mmggamefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mmggamefi.com/economy/mmc-governance-token/token-allocation-and-veiling-details.md).

# Token Allocation & Veiling Details

**Liquidity pool**: 5 million (5% out of total), 30% will be unlocked at launch.

**Seed round**: 10 million (10% out of total), 8% (800,000) will be unlocked at launch. After locking for 3 months, 4.38% (402,000) will be released monthly.

**IEO/ IDO**: 2 million (2% out of total), 2 million will be 100% unlocked at launch.

**Treasury**: 30 million (30% out of total). After locking for 6 months, 67% (2 million) will be unlocked quarterly.

**Team**: 20 million (20% out of total). After locking for 12 months, 69% (1.538 million) will be unlocked quarterly.

**Ecosystem**: 33 million (33% out of total), it will be permanently locked and released according to the usage function of DAO.


---

# 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://docs.mmggamefi.com/economy/mmc-governance-token/token-allocation-and-veiling-details.md?ask=<question>&goal=<endgoal>
```

`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.