> For the complete documentation index, see [llms.txt](https://rigworkz.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rigworkz.gitbook.io/docs/the-usdrogz-token-utility.md).
# The $ROGZ Token Utility
At the heart of the RigWorkZ ecosystem lies **$ROGZ** — a multi-utility, deflationary token that powers every layer of the marketplace’s economy. $ROGZ is more than just a payment asset; it serves as the **trust engine** of the platform, anchoring transparency, accountability, and community alignment between miners, investors, and the protocol itself. Every operator bonds $ROGZ to prove credibility before listing, every investor earns or redeems $ROGZ as tokenized mining yield, and every transaction recycles value back into the ecosystem through smart-contract-enforced buybacks, liquidity injections, and reward emissions.
This cyclical model ensures that each participant actively contributes to ecosystem growth while being rewarded for honest participation. A portion of all network activity — from performance fees to marketplace trades — is automatically directed to the **Ecosystem Treasury**, **Liquidity Pools**, **Operator & Staker Rewards**, and **Community Programs**, forming a closed economic loop where utility feeds sustainability. By embedding governance, bonding, and fee discounts directly into its design, $ROGZ unifies the incentives of all stakeholders under one verifiable system. Over time, as the platform transitions toward full DAO governance, $ROGZ will evolve into the core decision-making asset — giving holders the power to propose, vote, and shape the long-term trajectory of RigWorkZ itself.
***
---
# 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://rigworkz.gitbook.io/docs/the-usdrogz-token-utility.md?ask=&goal=
```
`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.
