> For the complete documentation index, see [llms.txt](https://greenpaper.games.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://greenpaper.games.gg/g3-token/ecosystem-utility/staking-rights.md).

# Staking Rights

Stakers can earn rights that distinguish users, grant them additional rights, and further augment their profiles and platform access to exclusive and public features.&#x20;

GAM3S.GG continues to aspire to grow as an all-in-one platform, which naturally means targeting users with different interests and preferences. Some users might be solely interested in discovering new games and keeping up with industry news. Others might be looking for more engaging quests and collecting rewards and XP to climb leaderboards. Similarly, other users might be scouting the analytics page and looking for trading opportunities across gaming projects. \[REDACTED]

Hence, utilizing "badges" or "rights" through staking $G3 tokens can allow us to personalize the platform experience depending on each user, allowing them to explore the features they're interested in far more deeply.&#x20;

Badges, or rights, are retained for as long as users’ tokens remain staked. With more features and, therefore, more specialized access over time, users can switch based on varying preferences while still preserving long-term alignment with platform growth. In addition, staking is not only targetted towards individual users - game studios and partners looking to leverage our infrastructure across quests, gaming identity layer, tournaments, \[REDACTED] and beyond will also be granted respective rights based on $G3 tokens staked and threshold requirements.


---

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