> For the complete documentation index, see [llms.txt](https://docs.wav-3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wav-3.com/welcome/quickstart/where-we-are.md). # Where We Are Early traction, explosive growth, and MVP momentum WAV.3 has just kicked off its MVP with explosive early traction: * **Launch Momentum:** Our Twitter presence surged to \~1,000 followers within 48 hours of going live, signaling strong market curiosity * **User Growth:** Over **5,000 users joined in the first 48 hours**, driven by grassroots referrals and KOL support * **MVP Bot Live:** Our Telegram MVP bot now lets users earn points from listening, and compete on a referral leaderboard — modeled on Grass.io’s viral growth loops * **Genesis Licenses:** Our Genesis License sale has opened, giving early supporters validator status, XP multipliers, and a baseline $WAV allocation * **$WAV3 Agentic Music Discovery by Virtuals TGE:** Our $WAV3 token launched on Virtuals Genesis and reached tier 2 pledging. $WAV3 opened at $700k Market Cap and peaked at $2M. This phase is about proving traction and gathering the data that powers our discovery engine. --- # 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://docs.wav-3.com/welcome/quickstart/where-we-are.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.