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

# Token Unlocking Schedule

**Initial Coin Offering (ICO) and Pre-ICO Phase**

* **Total Allocation for ICO/Pre-ICO**: 5% of the total supply (0.105 billion tokens).

**Post-ICO Distribution**

* **After ICO - Next 6 Months**: 5% of the total supply (0.105 billion tokens) will be released on 2+ exchanges.
* **Following 6 Months**: An additional 5% of the total supply (0.105 billion tokens) will be released on 5+ exchanges.

**Long-Term Release Plan**

* **Next 63 Months**: Promoter's stake will be released at a rate of 333.33K tokens every month, totalling 10% of the total supply (20.1 million tokens) over the next 63 months from TGE.

**Reserve Quota**

* **Total Allocation**: 5% of the total supply (0.105 billion tokens), set aside as a reserve quota.

**Cloud Mining**

* **Total Allocation**: 50% of the total supply (1.05 billion tokens) will be distributed through cloud mining over 480 months.


---

# 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://lither.gitbook.io/lither-whitepaper/tokenomics/token-unlocking-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.