> For the complete documentation index, see [llms.txt](https://docs.one-protocol.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.one-protocol.online/token-allocation.md).

# Token Allocation

A detailed breakdown of ONE token distribution and vesting schedules.

***

#### Allocation Breakdown

| Allocation Category      | Percentage |   Token Amount  | Vesting Period | Initial Release | Note                                                |
| ------------------------ | :--------: | :-------------: | :------------: | :-------------: | --------------------------------------------------- |
| **Community Incentives** |     50%    |    50,000,000   |     3 years    |       15%       | Liquidity mining, staking rewards, ecosystem growth |
| **Early Investors**      |     20%    |    20,000,000   |     2 years    |       10%       | Seed & private sale funding                         |
| **Team & Advisors**      |     15%    |    15,000,000   |     4 years    |       10%       | Core team, advisors, future hires                   |
| **Ecosystem Fund**       |     10%    |    10,000,000   |     5 years    |       25%       | Partnerships, integrations, grants                  |
| **Vault**                |     5%     |    5,000,000    |   No vesting   |       35%       | Emergency funds, insurance pool                     |
| **Total Supply**         |  **100%**  | **100,000,000** |      **-**     |      **-**      | **Max**                                             |

***

{% hint style="info" %}
**Key Takeaways**

* **Community First:** Over 50% of the total token allocation goes directly back into securing, mining, and expanding community incentives.
* **Long-Term Alignment:** The team, advisor, and ecosystem allocations are locked on multi-year vesting timelines (up to 5 years) to maintain long-term alignment with platform growth.
  {% endhint %}


---

# 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.one-protocol.online/token-allocation.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.