> 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 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://docs.playnance.com/white-label/w3caas-web3-casino-as-a-service/powered-by-usdgcoin.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.