> For the complete documentation index, see [llms.txt](https://clio-defi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clio-defi.gitbook.io/docs/tokenomics.md).

# Tokenomics

The Clio token aligns long-term participants — backers, builders, and users — across the protocol's lifecycle. The design favors operational longevity over launch-week excitement.

### Distribution

| #  | Allocation       | Share    | Purpose                             |
| -- | ---------------- | -------- | ----------------------------------- |
| 01 | Liquidity Pool   | 30%      | Sustained depth across BNB pairs    |
| 02 | Development      | 25%      | Engineering, audits, infrastructure |
| 03 | Seed Sale        | 20%      | Early backers · long unlock         |
| 04 | Team & Advisors  | 10%      | 12-month cliff · linear vest        |
| 05 | Ecosystem Growth | 10%      | Partnerships, content, education    |
| 06 | Treasury Reserve | 5%       | Strategic reserve, governed by DAO  |
|    | **Total**        | **100%** |                                     |

### Notes on the Distribution

#### No Retail Launch Event

There is no open retail launch round. Allocation rounds are private and limited; the open market unlocks through liquidity, not auction. We have observed repeatedly that broad retail launch rounds create launch-day price discovery problems that take months to settle. The trade-off — slower retail entry — is acceptable.

#### Seed Sale

The Seed Sale is the largest external allocation and carries the longest unlock schedule. Backers commit capital for a multi-year horizon; in exchange, they receive the deepest discount and the strongest information access during operation.

#### Team & Advisors Vesting

Team and advisor tokens carry a 12-month cliff followed by a 24-month linear vest, totaling 36 months from the Token Generation Event. No team member receives any tokens before month 13. We chose this schedule deliberately: by the time the first team tokens unlock, the protocol will either have demonstrated traction or it will not. Either outcome should be reflected in the team's incentive curve.

#### Treasury Reserve

The Treasury Reserve is multi-sig controlled at launch and will pass to DAO governance after the first audited fiscal cycle (approximately month 18). The reserve is intentionally small — 5% — to discourage governance capture games while still providing flexibility for ecosystem investments.

#### Liquidity Pool

The Liquidity Pool allocation is the largest single allocation. It is deployed into BNB-paired pools at launch and managed by Clio's liquidity strategy. A portion will move to permanent ownership over time, structured as protocol-owned liquidity.

#### Unlock Schedule

The detailed unlock schedule (per category, per quarter) is published in the project's GitHub repository and updated quarterly. The first unlock event occurs at the Token Generation Event in Phase II of the [Roadmap](broken://pages/c1d5e87a71bf8aba5c652db0351031434fc9b7f7).


---

# 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://clio-defi.gitbook.io/docs/tokenomics.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.