> For the complete documentation index, see [llms.txt](https://docs.ec-cube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ec-cube.io/tokenomic/2.-token-distribution.md).

# 2. Token Distribution

The maximum supply of $ECT tokens is set at 1000,000,000. and it will be gradually released to participants, investors, community, and reserves within the Ec³ ecosystem, as shown in the table below:

<figure><img src="/files/D4vQe3a0Qf5Qot188KeB" alt="" width="563"><figcaption><p>$ECT token distrubution</p></figcaption></figure>

<figure><img src="/files/f1zpyxkssBB6cLoTYCAT" alt=""><figcaption><p>$ECT token distrubution</p></figcaption></figure>

For any institution, whether it is an angel round or a Series A, upon reaching the TG1 phase, which is the listing on a centralized exchange, there will be an immediate release of 10% of the shares, followed by a six-month lock-up period. The remaining 90% of the shares will be released gradually on a monthly basis thereafter.

The release schedule for the team's shares is delayed by six months compared to the institutions. This means that while the institutions will have an immediate release of 10% of their shares at the TG1 phase, the team's shares will begin to be released in a linear fashion six months later, on a monthly basis.


---

# 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.ec-cube.io/tokenomic/2.-token-distribution.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.
