> 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-allocation-and-utility.md).

# Token Allocation and Utility:

1. **Cloud Mining (50%):** Half of the total token supply is dedicated to cloud mining, providing an accessible opportunity for users to mine Lither tokens and participate in network security.
2. **ICO (5%):** A small portion of tokens is allocated for an initial coin offering (ICO) to fund development and attract early investors.
3. **Liquidity (10%):** Ensuring a liquid market, 10% of tokens are allocated for liquidity provision on decentralized exchanges, fostering smooth trading.
4. **Ecosystem (10%):** These tokens are reserved to build and expand the Lither ecosystem, including partnerships, integrations, and dApp development.
5. **Community Mining (0.5%):** A fraction of tokens is set aside for community mining activities, encouraging active participation and engagement.
6. **Airdrop (1%):** Lither believes in rewarding the community. We allocate 1% of tokens for airdrops, offering surprises to our dedicated users.
7. **Founder (10%):** The founding team is committed to the project's success, with 10% of tokens allocated. These tokens will have a vesting period to ensure alignment with the project's long-term goals.
8. **Advisor (5%):** Advisors play a crucial role in shaping our strategy. We allocate 5% of tokens for advisors, also subject to vesting.
9. **KOL's (Key Opinion Leaders) (5%):** Building a strong community requires influencers. 5% of tokens are reserved for KOLs who actively contribute to Lither's growth.
10. **Private Sale (3.5%):** To fund early development and partnerships, a small portion of tokens is available through private sale events.


---

# 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-allocation-and-utility.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.