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

# Emission Schedule

All **888,888,888 $HELI** tokens will be supplied following a linear decay emission model. This linear model leads to a more stable distribution and ideally less fluctuations in the token value. To spread the distribution according to the growth needs of the company, certain allocation buckets follow a defined cliff and vesting period. The Team & Advisor bucket is barred with a 2 year cliff and 3 year vesting schedule, as we want to show our community the strong level of commitment that the team has for HeliSwap and to build out a sustainable and mature product over time.

### Vesting with time - Hedera Hashgraph

The Hedera Hashgraph, though somewhat related to alternative blockchains, is not a blockchain in itself as it contains no blocks. The Hashgraph algorithm rather works with timestamps, which are then used as the consensus timestamp for a transaction. For HeliSwap this means that the $HELI token does not vest by block, but with time (even seconds) - this also includes the rewards earned on the platform.

### Emissions schedule over the next 5 years

<figure><img src="/files/w5NU8Co6oRFUQwx4nKCX" alt=""><figcaption></figcaption></figure>

You can find more detailed information under the [Token Allocation](/tokenomics/token-allocation.md#detailed-view)


---

# 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.heliswap.io/tokenomics/emission-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.