> 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/business-and-revenue-model.md).
# Business & Revenue Model
RigWorkZ operates as a two-sided escrow-governed marketplace:
* Investors buy fractional mining shares in USDC/USDT, secured via NFT ownership and escrow contracts.
* Operators list hardware by bonding ROGZ, verified by real-time supervisor scripts and API integrations.
* RigWorkZ Treasury sustains itself via transparent platform fees, a portion of which recycles back into the ecosystem through buybacks, burns, and staking incentives.
* Dual-payment policy: Users can always transact in USDC/USDT; paying fees in ROGZ unlocks discounts. Non-ROGZ fees contribute to the ROGZ liquidity pool.
* ROGZ Token acts as a loyalty and governance layer, powering discounts, insurance, bonding, and gamification.
**Revenue Model**
RigWorkZ generates revenue through a multi-stage fee structure:
These fees create a recurring, sustainable income stream that drives platform growth, scalability, and continued innovation.\
\
Distribution of Treasury Revenue:
* 40% → ROGZ Ecosystem & Stakers: Used for staking rewards, loyalty tiers, and XP gamification.
* 40% → Reinvestment: Audits, product upgrades, partnerships, liquidity, and ecosystem growth.
* 20% → RigWorkZ Core Team: For operations, compliance, and strategic expansion.
Deflationary Loop:
* A portion of collected USDC/USDT fees is always used to buy back and burn ROGZ.
* Operators/investors using ROGZ for fee payments unlock discounts, adding continuous demand pressure.
* Policy parameterization: Burn %, insurance allocation %, and fee discounts are governed by ROGZ token holders (DAO) and can adapt to market cycles.
Insurance Pool:
* Small % of treasury revenue is directed to a ROGZ-backed insurance vault, compensating investors if verified operators default.
---
# 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/business-and-revenue-model.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.
