# Token Distribution

### Summary

* Max supply of Qi tokens (hard cap): 200M&#x20;
* Early partners: <5% released linearly for 18 months
* Keeper allocation: \~10% total vested over 3 years
* Community Distribution: 85%

## Tokenomics

### **Community distribution (85%)**&#x20;

The lion's share of Qi tokens will go to the community. We want QiDao to be owned and run by the community that participates in the QiDao project. Below is the breakdown of how Qi tokens will be given to the community.

#### *Community Treasury*

These are Qi tokens owned by the community. The community can vote on how to use these tokens.

* Vesting - will be vested linearly at every Polygon block over a period of 3 years (starting launch) in line with the schedule below:
  * Year 1: 50% of the treasury tokens vested
  * Year 2: 30% of the treasury tokens vested
  * Year 3: 20% of the treasury tokens vested

### **Early Partners (5%)** &#x20;

The community can align incentives with strategic partners through the distribution of Qi tokens. Qi tokens awarded in this distribution will be vested linearly for 18 months.

### **Keeper incentive (10%)**&#x20;

The role of Keepers is to provide direction to the network in its early stages and to maintain and upgrade the codebase following governance votes. Keeper incentives are vested over 3 years linearly and can be stopped by governance votes if the team does not perform accordingly.<br>


---

# Agent Instructions: 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:

```
GET https://docs.mai.finance/tokenomics-1/tokenomics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
