> For the complete documentation index, see [llms.txt](https://docs.kodo.exchange/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kodo.exchange/overview/tokenomics/emissions.md).
# Emissions
The initial total supply of `$KODO` tokens is 400M. Each epoch, `$KODO` will undergo the following three forms of supply expansion:
* **Weekly Emissions**: Weekly emissions start at 15M `$KODO` (3.75% of the initial supply), with a release amount decreasing by 1% per week. All released `$KODO` tokens are allocated to Liquidity Providers (LPs).
* **Rebase**: `$veKODO` holders receive a `$KODO` rebase during each epoch proportional to both the LP emission and the `$KODO` lock-up ratio, reducing vote power dilution for `$veKODO`. `$veKODO` rebase does not affect weekly emissions distributed to liquidity providers.
The calculation formula for the rebase is structured to provide greater rewards to `$veKODO` holders when the lock-up ratio decreases, incentivizing further lock-ups:
$$
\text{{Rebase}} = \text{{Weekly Emissions}} \times \left(1 - \frac{{\text{{veKODO.Total Supply}}}}{{\text{{KODO.Total Supply}}}}\right)^2 \times 0.5
$$
* **Team Emissions:** Kodo will ensure its long-term sustainability by having a dedicated team focused on supporting the product decentralization, documentation, community, and ecosystem. To cover ongoing expenses and all the upcoming development efforts, \~3% of the emissions will be going to the team address.
### Emission Schedule
### Distribution Rules for Weekly Emissions
* Weekly `$KODO` rewards are allocated to liquidity pools based on `$veKODO` vote power ratios for each epoch. LPs earn rewards in proportion to their liquidity contribution and duration in each pool.
* `$KODO` rewards are streamlined and accumulative, and can be withdrawn as liquid `$KODO` at any time, offering flexibility and immediate value to participants.
---
# 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.kodo.exchange/overview/tokenomics/emissions.md?ask=&goal=
```
`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.