# Tokenomics 

CHI is the native token that powers the Chi Protocol, serving essential functions such as boosting, liquidity provision, and governance. As an ERC-20 governance token, CHI enables its holders to manage the protocol and its associated risks, ensuring stability, transparency, and efficiency.

The voting power of CHI holders is proportional to the amount of CHI they boost and the duration of the lock-up period. The more CHI tokens boosted and the longer the duration, the greater the voter’s influence in governance decisions.

{% hint style="success" %}
By boosting CHI, users obtain veCHI, which grants them voting power and access to rewards such as stETH and CHI. Additionally, users can provide liquidity in the CHI/ETH pair on Uniswap v2 and stake the LP tokens to earn stETH, weETH, and CHI incentives. This structure ties CHI to real value, as reflected by the protocol's reserves, and allows CHI token holders to benefit from the growth of the USC reserves. The larger the reserves, the greater the incentives to boost CHI and provide liquidity, making CHI a valuable asset within the protocol.
{% endhint %}

## Token Allocation

At launch, CHI had an initial supply of **100,000,000** tokens, distributed as follows:<br>

<figure><img src="/files/l6OGoSiFEVuvmRllveeH" alt=""><figcaption><p>Tokenomics</p></figcaption></figure>

<figure><img src="/files/6sYXOcZCy7zA4vWRmTgE" alt=""><figcaption><p>Allocations</p></figcaption></figure>


---

# 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://chi-protocol.gitbook.io/chi-docs/chi/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.