> 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/issuer-identification.md). # Issuer Identification This section identifies the legal entity responsible for the creation, management, and distribution of the $RAVE token. ### Issuer Information * **Name:** RaveDAO Ltd. * **Registered Address:** Trinity Chambers, PO Box 4301, Road Town, Tortola, British Virgin Islands\ VG * **Registration Date:** 2025-06-25 * **Company Number / Identifier:** 2179629 * **Email Address:** ### Business Activity RaveDAO Ltd. is responsible for the creation, management, and distribution of the $RAVE token. The total supply of $RAVE is capped at 1,000,000,000 tokens. The token allocation is designed to support community programs, ecosystem expansion, core contributors, strategic partners, liquidity, and philanthropic initiatives aligned with RaveDAO’s mission to merge entertainment, blockchain innovation, and social impact. --- # 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/issuer-identification.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.