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

# LiFi Tokenomics

| **Category**         | **Allocation (%)** | **Purpose**                                                                  |
| -------------------- | ------------------ | ---------------------------------------------------------------------------- |
| Team Supply          | 5%                 | Locked for 12 months, then gradually vested over the following 12 months     |
| Marketing Supply     | 10%                | Funding marketing campaigns, partnerships, community growth                  |
| Burned Tokens        | 25%                | Permanently burned after launch to reduce total supply and increase scarcity |
| Rewards & Incentives | 10%                | Distributed for staking, referrals, user engagement, and ecosystem growth    |
| Liquidity Pool       | 50%                | Used to provide initial liquidity on DEX/CEX platforms and stabilize trading |

***

#### **Token Allocation Notes**

| **Aspect**           | **Details**                                                                |
| -------------------- | -------------------------------------------------------------------------- |
| Total Supply         | Fixed (To Be Announced)                                                    |
| Burn Mechanism       | One-time post-launch burn of 25% of total supply                           |
| Team Vesting         | 12-month lock, followed by 12-month linear vesting                         |
| Liquidity Strategy   | LP tokens may be locked or burned based on governance or roadmap decisions |
| Rewards Distribution | Handled via smart contracts based on community and user activity           |


---

# 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://lifi-chrome-tracker.gitbook.io/lifi-chrome-tracker-docs/tokenomics/lifi-tokenomics.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.