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

# 7.  Distribution

Here is the table extracted from the image:

| **Category**             | **Percentage** | **Tokens (LQX)** | **Purpose & Notes**                    |
| ------------------------ | -------------- | ---------------- | -------------------------------------- |
| Presale - All 4 Rounds   | 28%            | 280,000,000      | Distributed to early investors         |
| Yield Farming Rewards    | 27%            | 270,000,000      | Paid to users who provide liquidity    |
| DEX Liquidity Pool       | 18%            | 180,000,000      | Ensures trading liquidity at launch    |
| Ecosystem & Development  | 12%            | 120,000,000      | Protocol growth - community controlled |
| Airdrop Allocation       | 2%             | 20,000,000       | Community growth & early user rewards  |
| Community Treasury (DAO) | 10%            | 100,000,000      | Governed by LQX token holders          |
| Security & Audit Fund    | 3%             | 30,000,000       | Smart contract audits, bug bounties    |
| Insurance / Safety Fund  | 2%             | 20,000,000       | Emergency protocol safety net          |
| TOTAL                    | 100%           | 1,000,000,000    |                                        |

⚠  CRITICAL FOR INVESTORS: There is NO team allocation in LiquidX. Zero percent goes to founders, developers, or advisors. The Development Fund is held in a community-controlled multisig wallet - meaning no single person can access or move these funds without community approval. This is the gold standard of decentralized protocol design.

<br>


---

# 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://liquidx-3.gitbook.io/liquidx-whitepaper/7.-distribution.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.