# WAVE Esports

## Making Waves

<figure><img src="/files/59sr2Fq9nZ0YQ54Gv1jo" alt=""><figcaption><p>WAVE Esports</p></figcaption></figure>

Founded in July 2019, WAVE has already become one of the biggest esports organisations in Europe. With more than 7m followers across their social media, they've quickly grown to be one of the leading lifestyle and esports brands in the DACH region and beyond. WAVE have a world-class professional Fortnite team and have recently branched out into *Riot Games'* tactical shooter, Valorant.

We'll be working together with WAVE to create an esports engagement platform through using our platform's DAO tooling. WAVE Guild will be structured as a DAO and will provide fans new modes of interaction, rewards and incentives while allowing them to engage with the organisation directly through the platform, all available on GameDAO.&#x20;

*"We want to offer our community opportunities to be directly involved and create new outlets for fan engagement." - Cris Mendez, founder of WAVE Esports.*

This platform will be used as a blueprint to provide the engagement platform to future esports organisations to help them build more sustainable business models, engage their fans, and reach their true potential.

The initial step with the partnership will be the development of a 'battlepass' prototype that will reward fans for their interactions-with both free and premium versions, the battlepass reward system will ensure that all fans are rewarded no matter what.


---

# Agent Instructions: 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:

```
GET https://docs.gamedao.co/partnerships/wave-esports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
