> 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/support/frequently-asked-questions.md).

# Frequently Asked Questions

## WAV.3 FAQ

<details>

<summary>What is WAV.3?</summary>

WAV.3 is like [Grass.io](https://grass.io) for music discovery and streaming.\
Use our [Telegram MVP bot](https://t.me/wav3appbot) to join, earn points through referrals, and climb the leaderboard while helping shape the discovery network.

</details>

<details>

<summary>How do I join the MVP?</summary>

Use our Telegram bot at [t.me/wav3appbot](https://t.me/wav3appbot) to join, get your referral code, and start earning points.

</details>

<details>

<summary>How does the referral system work?</summary>

Share your referral link from the bot. Each real user who joins through your link earns you **NetworkXP** points.

</details>

<details>

<summary>How do I see my stats?</summary>

Check your **leaderboard position and profile** inside the Telegram bot. It updates automatically as you and your referrals earn points.

</details>

<details>

<summary>When can I link my Spotify and start earning TasteXP?</summary>

**Soon.** We are actively building this integration, and your referral score reflects your eligibility to be in the **top 20 first beta users** when the integration is live.

</details>

<details>

<summary>Why only 20 beta users?</summary>

Spotify only allows us **20 users until we prove traction**. That’s why our early growth is essential — it unlocks access to the full Spotify API.

</details>

<details>

<summary>What are Genesis Licenses?</summary>

Genesis Licenses are **lifetime validator credentials** for WAV.3.\
There are only **1,000 total**, starting at **$250 and rising +$5 each sale**.\
They give holders points multipliers and validator rights within the network.

</details>

<details>

<summary>Can I trade Genesis Licenses right now?</summary>

Not yet — they are **locked until all 1,000 are sold**, ensuring price integrity and aligned incentives during this bootstrap phase.

</details>

<details>

<summary>How fast is WAV.3 growing?</summary>

In the first 48 hours:

* \~1,000 :contentReference\[oaicite:5]{index=5} followers
* 2,000+ users joined the MVP\
  This early traction proves demand for a new music discovery model.

</details>

<details>

<summary>Does WAV.3 replace traditional streaming platforms?</summary>

No — WAV.3 will build on top of existing DSPs like Spotify. You will continue listening where you already do, while WAV.3 rewards your activity.

</details>

<details>

<summary>Is my data secure?</summary>

Yes. WAV.3 will only read anonymized listening metadata (track IDs, timestamps) from your DSP and will never access personal content.

</details>

<details>

<summary>What’s next for WAV.3?</summary>

WAV.3 is preparing to **evolve beyond the MVP** into a new kind of discovery layer, which will involve:

* AI-driven agentic music discovery
* Anonymous merit-based song launches
* On-chain song assets
* Personalized TasteGraphs

Details will be revealed gradually.

</details>


---

# 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/support/frequently-asked-questions.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.