# Ecosystem Utility

$G3 was designed to fuel the entire GAM3S.GG ecosystem ranges from existing features to the upcoming ones and future ones beyond. To simplify how we view the overall token utility and overall functionality, you can view it in four different utility categories:

<table><thead><tr><th width="218">Utility</th><th>Description</th></tr></thead><tbody><tr><td><strong>Stake</strong> for Rights</td><td>Holders can stake $G3 tokens for specific platform rights, which provide exclusive feature access within the platform. </td></tr><tr><td><strong>Redeem</strong> for Rewards</td><td>Holders can use $G3 tokens to acquire seasonal premium battle passes and unlock greater rewards from the best games across the ecosystem. </td></tr><tr><td><strong>Engage</strong> with the Platform</td><td>Holders use the $G3 token to transact with the platform, such as participating in tournaments and trading on the marketplace. </td></tr><tr><td><strong>Govern</strong> the Platform</td><td>Holders will be able to decide on the asset makeup of the rewards warchest, and influence feature decisions, ultimately shaping the platform's future using their $G3 tokens.</td></tr></tbody></table>

Each of these utilities plays an important role, with additional utility and utilization opportunities scheduled to roll out over the next few years as the platform continues to evolve and develop.&#x20;

To further understand each of the utilities, kindly refer to the following subsections.


---

# 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://greenpaper.games.gg/g3-token/ecosystem-utility.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.