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

# Emissions Schedule

**100% of ALL emissions go to gauges**, there are no team emissions or other distributions. Full decentralization of the emission distribution is the main priority.

There is a 1% exponential decay week over week, reducing emissions in perpetuity.

{% hint style="success" %}
The emissions schedule will be adjusted up and down based on market demand, and to prevent over/under inflation to remain competitive.
{% endhint %}

The formula to calculate an Epoch's emissions is:

$$
Emissions{(t)} = E\_{0}\ \*\ (e^{-rt})
\ \ \ t = Epochs \ E\_{0} = X \ -r = decay \ coefficient
$$

Alternatively, a user can calculate the emissions for an epoch based on the previous, as such:

$$
Emissions(epoch(N)) \ = Emissions(N-1)  \ \* (1.00-decay)
$$


---

# 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.cleo.exchange/cleo-tokenomics/emissions-schedule.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.
