> 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/impact-metrics.md). # Impact Metrics **Metrics:** * Attendance: 100,000+ participants across 5 countries in 2024–2025. * Wallet Onboarding: 50,000+ NFT tickets issued through our ticketing partner PLVR. * Social Reach: 150M+ impressions from Singapore & Dubai activations alone. * Artists Engaged: 40+ DJs and performers, from global top-10 DJs to K-pop stars and up and rising talents. * Philanthropy: 20% of event proceeds redirected to *Rave for Light* beneficiaries. **Case Studies:** * Tilganga Eye Center (Nepal): Supported 400+ cataract surgeries annually. * Nalanda West (Seattle): Funded meditation programs impacting 150+ participants per year. Impact is not an afterthought — it is woven into the culture. --- # 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/impact-metrics.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.