> For the complete documentation index, see [llms.txt](https://ravedao.gitbook.io/ravedao-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ravedao.gitbook.io/ravedao-whitepaper/readme/ravedao-tokenomics/introducing-usdrave.md).
# Introducing $RAVE
### Token Allocation
The total supply of 1 billion $RAVE tokens forms the foundation of RaveDAO’s cultural economy. The allocation is structured to support long-term sustainability, rewarding real participation and ensuring growth is distributed across the community.
#### **Overview**
* Community (30%) : Empower local chapters, builders, and loyal fans to grow the global community through governance grants, incentives, and rewards.
* Ecosystem (31%) : Drive brand/ecosystem integrations, partner activations, and technology infrastructure for global user acquisition and onboarding.
* Initial Airdrop (3%) : Initial Airdrop to previous RaveDAO event attendees and contributors.
* Foundation / Impact Pool (6%) : Long-term reserves for philanthropy (e.g. Rave for Light) and other initiatives governed by the DAO.
* Team & Co-Builders (20%) : Incentivize founding team, core contributors, strategic advisors and long-term collaborators who power the ecosystem’s evolution.
* Early Supporters (5%) : Recognize and reward early believers and partners who helped bootstrap the movement.
* Liquidity (5%) : Ensure smooth market access and stability for participants across exchanges.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://ravedao.gitbook.io/ravedao-whitepaper/readme/ravedao-tokenomics/introducing-usdrave.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
