> 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/future-of-ravedao.md).

# Future of RaveDAO

**2025–2027 Roadmap**

* 2025: Flagship events at Dubai and Singapore Token2049. Chapter pilots in Asia (Bitcoin Asia, Korea Blockchain Week etc), Europe (Amsterdam Dance Event), and US (Miami Winter Conference).
* 2026: Scale to Hong Kong, Los Angeles, and New York. Grow annual attendance to 100,000+.
* 2027: Achieve 300,000+ annual attendees across 50+ chapter events. Cement RaveDAO as the decentralized Live Nation + TEDx of entertainment.

**Scaling Chapters Globally**

Each chapter strengthens the global brand while remaining true to its culture. This model ensures both grassroots ownership and global resonance.

**Expanding the Sandbox**

Beyond music, RaveDAO will extend into gaming, sports, digital creators, and education — making entertainment the most accessible and impactful entry point to Web3.


---

# 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/future-of-ravedao.md?ask=<question>&goal=<endgoal>
```

`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.