> For the complete documentation index, see [llms.txt](https://whitepaper.challenge.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.challenge.gg/challenge/platform/currencies.md).

# Currencies

<figure><img src="/files/8YERlrZ1yJldFmyIqyXS" alt=""><figcaption></figcaption></figure>

### Embracing Diversity in Cryptocurrencies

In an increasingly digital world, Challenge.gg aims to create an environment where everyone, regardless of their choice of games or cryptocurrencies, can participate and reap the benefits of an engaging and profitable gaming ecosystem.

Our platform brings a variety of games to the table, ensuring that players with different tastes find something that resonates with them. With a wide array of games spanning various styles and categories, players can indulge in their favourite pastimes and share in the excitement of competitive gaming.

Moreover, Challenge.gg empowers users by giving them the opportunity to actively contribute to its evolution. Users can vote and participate in development decisions, be part of thrilling tournaments, and even stake their digital assets to earn passive income from the ecosystem's revenue.

### The Power of Diverse Cryptocurrencies

Our network recognises the vital role of cryptocurrencies in expanding our user base and player community. Thus, we are dedicated to fostering an environment conducive to multiple cryptocurrencies, starting with Ethereum, our foundational network.

The Challenge.gg tournament system is built on the Ethereum network, allowing players to join tournaments and access features within the ecosystem using Ether (ETH).

### Expanding Horizons with Multiple Chains and Currencies

However, our ambitions don't stop at Ethereum. We are committed to building our tournament system across different blockchain networks, each supporting its unique currency.

The first of these expansions will introduce $Challenge Token, our native token, followed by the integration of Tether (USDT).

Next on the roadmap is the incorporation of Binance Smart Chain (BSC), enabling users to play using Binance Coin (BNB).

This roadmap aligns with our ultimate goal to onboard a variety of currencies, making it easier for players to interact with our ecosystem using their preferred digital asset.

Our platform also accommodates developers looking to integrate their web3 games into our ecosystem. This flexibility ensures that developers can utilize their choice of currency for their games, reinforcing our commitment to a truly inclusive and comprehensive gaming network.

At Challenge.gg, we believe in the power of diversity, not just in gaming, but also in the cryptocurrencies that power our platform. Our mission is to build a universal platform that brings players, developers, and digital assets together to create a vibrant, engaging, and profitable gaming ecosystem.

### When?

Check out our ROADMAP:

{% content-ref url="/pages/O6kuxIxPjHk2d6BnprY1" %}
[ROADMAP](/roadmap/vision.md)
{% endcontent-ref %}


---

# 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://whitepaper.challenge.gg/challenge/platform/currencies.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.