> 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.md). # RaveDAO Whitepaper Welcome to your team’s developer platform > (2026 Sept Version) ## **Abstract** RaveDAO is a global music, culture, and technology operating system built around live entertainment, community participation, digital access, and social impact. The live entertainment industry continues to capture global attention at scale, while Web3 continues to search for more intuitive, culturally relevant paths to mainstream adoption. RaveDAO exists at the intersection of these two movements. It uses music and live experiences as the cultural layer through which communities can discover new forms of participation, ownership, digital identity, rewards, payments, and governance. Since launching its first sold-out event in Dubai in 2024, RaveDAO has expanded across Asia, the Middle East, Europe, and North America, supporting and producing more than **100 global events** across markets including Dubai, Singapore, Korea, Hong Kong, Bangkok, Amsterdam, Miami, and Brussels. The ecosystem has brought together more than **200,000 attendees** across its events and built a broader community reach of over **1M+** across Instagram, Telegram, WeChat, X, and partner communities. RaveDAO has worked with internationally recognized artists across electronic music, including Vintage Culture, Don Diablo, Charlotte de Witte, MORTEN, Miss Monique, ARTBAT, Chris Avantgarde, Lilly Palmer, Eli Brown, Monolink, Massano, and others. The ecosystem has also developed partnerships across music, entertainment, Web3, lifestyle, and media, including Tomorrowland / Terra Solis, Warner Music, Amsterdam Dance Event, 1001Tracklists, DJ Lovers Club, 808 Festival, Bitget Wallet, KuCoin Pay, NOWPayments, Red Bull, Pernod Ricard, and other ecosystem partners. In the future, RaveDAO continues to evolve from an event-driven cultural IP into a broader entertainment and technology ecosystem. Its focus includes global event expansion, artist touring, community-led event formats, payment integrations, digital fan engagement, and the development of future governance infrastructure for ecosystem participation. Beyond live entertainment, RaveDAO channels community energy toward real-world impact. Previous initiatives have supported more than **400 cataract surgeries in Nepal** and more than **150 mindfulness programs in the United States**. Through Rave for Light and other social-impact initiatives, selected eligible events may contribute attention, resources, and eligible net proceeds toward charitable or social-impact initiatives, subject to applicable law, event economics, partner arrangements, and operational feasibility. RaveDAO is not just an event brand. It is an entertainment sandbox where music, community, technology, and real-world impact come together. --- # 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.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.