# Tokenomics

CLO is the native token of the Clovis protocol, used for governance and aligning the community with the long-term growth of the network.

### Supply

The total supply of CLO is fixed at **1,000,000,000** tokens.

The Token Generation Event (TGE) occurred in **October 2025**. At Genesis, **129,100,000 CLO (12.91%)** entered circulation. The remaining **870,900,000 CLO (87.09%)** is subject to a scheduled release over the four years following TGE, reaching full circulation in **September 2029**.

### Allocation

| Category  | Percentage |
| --------- | ---------- |
| Ecosystem | 30.0%      |
| Treasury  | 20.5%      |
| Team      | 15.0%      |
| Investors | 10.0%      |
| Marketing | 6.5%       |
| Airdrop   | 5.0%       |
| Advisors  | 5.0%       |
| Liquidity | 4.0%       |
| Exchange  | 3.0%       |
| IDO       | 1.0%       |

### Allocation Details

#### Ecosystem (30%)

Grants and incentives for LPs, builders, partners, integrations, and strategic growth programs.

#### Treasury (20.5%)

DAO-controlled reserves for operations, strategic investments, and runway.

#### Team (15%)

Allocation for core contributors.

#### Investors (10%)

Allocation for early backers funding initial development.

#### Marketing (6.5%)

Budget for brand growth, user acquisition, partnerships, and promotional campaigns.

#### Airdrop (5%)

Distributed to early users and community to reward adoption and bootstrap usage.

#### Advisors (5%)

Tokens for advisors providing strategic guidance.

#### Liquidity (4%)

Reserves for on-chain pools and protocol liquidity to ensure deep, stable markets.

#### Exchange (3%)

Tokens reserved for CEX liquidity.

#### IDO (1%)

Public sale allocation for launchpad participants and initial market distribution.

### Vesting Schedule

| Category  | % Unlock at TGE | Lock-up Duration | % Unlocked at Cliff | Unlock Duration |
| --------- | --------------- | ---------------- | ------------------- | --------------- |
| Ecosystem | 0%              | None             | 0%                  | 36 months       |
| Treasury  | 0%              | 2 months         | 0%                  | 36 months       |
| Team      | 0%              | 12 months        | 0%                  | 24 months       |
| Investors | 0%              | 12 months        | 0%                  | 24 months       |
| Marketing | 100%            | None             | 0%                  | None            |
| Airdrop   | 40%             | None             | 0%                  | 4 months        |
| Advisors  | 0%              | 12 months        | 0%                  | 36 months       |
| Liquidity | 100%            | None             | 0%                  | None            |
| Exchange  | 13.7%           | None             | 0%                  | 2 months        |
| IDO       | 0%              | 1 month          | 50%                 | 6 months        |

<figure><img src="/files/08zlNEyQ9o6WfYUByVtU" alt=""><figcaption></figcaption></figure>

### Contract Addresses

| Network   | Address                                                                                                            |
| --------- | ------------------------------------------------------------------------------------------------------------------ |
| BNB Chain | [0x81D3A238b02827F62B9f390f947D36d4A5bf89D2](https://bscscan.com/token/0x81D3A238b02827F62B9f390f947D36d4A5bf89D2) |


---

# 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.yei.finance/clo-token/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.