> 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.md). # RaveDAO Tokenomics Introducing $RAVE: The Pulse Behind a Decentralized Cultural Movement Every cultural movement begins with rhythm, a pulse that carries people toward something bigger than themselves. In the 90s, that rhythm moved through warehouses and dancefloors. Today, it moves through networks and code. What has always stayed constant is the human desire to connect. RaveDAO exists for that connection. What began as a global series of live gatherings in cities like Singapore, Dubai, Seoul, Miami, Hong Kong, Brussels, Bangkok, and Amsterdam has grown into a network where entertainment meets infrastructure. RaveDAO connects artists, organizers, and fans through a shared system that blends cultural experience with on-chain participation. Now, with the launch of $RAVE, that network gains its own economy. $RAVE is the coordination layer that links every chapter, event, and creator within the ecosystem. It powers governance, rewards, and real-world activity such as payment, turning culture itself into an active protocol. --- # 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://ravedao.gitbook.io/ravedao-whitepaper/readme/ravedao-tokenomics.md?ask=&goal= ``` `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.