> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/white-label/w3caas-web3-casino-as-a-service/powered-by-usdgcoin.md).

# Powered by $GCOIN

$GCOIN is the utility token that powers the Playnance ecosystem, fueling rewards, loyalty programs, affiliate payouts, and governance across every W3CaaS platform.

***

{% stepper %}
{% step %}
**Utility**

Access platform services and ecosystem-level functionality.
{% endstep %}

{% step %}
**Rewards**

Players and operators earn GCOIN through qualifying platform activity.
{% endstep %}

{% step %}
**Staking**

Stake GCOIN to participate in ecosystem growth and unlock yield mechanisms.
{% endstep %}

{% step %}
**Ecosystem Participation**

GCOIN connects the commercial and operational layers of the Playnance platform.
{% endstep %}
{% endstepper %}

***

* **Player rewards** — built-in loyalty mechanics, including cashback, missions, and tiered bonuses that drive retention.\ <br>
* **Affiliate payouts** — on-chain revenue share to partners, transparent, performance-based, and automatic.<br>
* **Operator incentives** — boosted rewards funded by the ecosystem, not the operator's margin.<br>
* **Governance** — $GCOIN holders vote on protocol upgrades, treasury, and partner allocations.<br>
* **Staking** — $GCOIN can be locked to earn passive rewards.<br>
* **Cross-platform utility** — one token spans every Playnance operator: casino, sportsbook, predictions, and beyond.<br>

{% hint style="info" %}
$GCOIN utility token is audited by CertiK and held by 1M+ holders across the ecosystem.
{% endhint %}

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.playnance.com/white-label/w3caas-web3-casino-as-a-service/powered-by-usdgcoin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.