> 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/earnings-fees-and-payout-mode.md).

# Earnings, Fees, and Payout Mode

**Operator Earnings Overview**\
At the core of RigWorkZ lies a fair, transparent, and performance-driven earnings structure designed to align operator success with investor confidence. Every payout, fee, and distribution is handled by on-chain smart contracts, ensuring that returns are not only accurate but verifiable in real time.

RigWorkZ’s model ensures that operators maintain control over their revenue while rewarding verified performance and reliability. The result is a frictionless ecosystem where capital, uptime, and trust are continuously reinforced by transparent, automated flows.

**Earnings Breakdown**\
Operators retain 97% of their verified mining output, while investors receive proportional $ROGZ rewards based on their NFT-backed shares, which is through a calculate input of the bonded $ROGZ as collateral\
\ <mark style="color:$info;">A 3% performance fee is automatically deducted by the smart contract to the RigWorkZ platform during each payout cycle to sustain validation services, escrow operations, and compliance automation.</mark>

**Fee Architecture:**

| Fee Type             | Rate                   | Who Pays             | Trigger                          | Purpose                                            |
| -------------------- | ---------------------- | -------------------- | -------------------------------- | -------------------------------------------------- |
| Success Fee          | 3%                     | Operator             | Upon completion of capital raise | Covers escrow automation and compliance            |
| Performance Fee      | 3%                     | Auto-deducted        | Each verified payout cycle       | Funds validation, oracles, and reward distribution |
| Secondary Market Fee | 5%                     | Purchaser → RigWorkZ | Every NFT/share resale           | Supports liquidity and $ROGZ buybacks              |
| Bonded $ROGZ Deposit | $100–$500 (refundable) | Operator             | Rig listing                      | Replaces listing fees with refundable collateral   |

Unsold or idle hashrate remains fully under operator control and continues mining normally.

**The Token and Ecosystem Flow**

$ROGZ is the heartbeat of the RigWorkZ ecosystem — powering bonding, staking, governance, rewards, and fee redistribution.

Each on-chain $ROGZ transaction contributes a 5% ecosystem fee, automatically routed through smart contracts to sustain liquidity, rewards, and platform operations.

Distribution of the 5% Ecosystem Fee:

* 60% to the Platform Treasury for infrastructure, audits, and development
* 25% to the $ROGZ Liquidity Pool to stabilize markets
* 10% to Operator and Staker Rewards for verified uptime and participation
* 5% to Community and Referral Programs supporting ambassador initiatives

All fee flows are transparent and verifiable on-chain.

**Verification Layer**

RigWorkZ’s verification system ensures complete data integrity across all listings.

* API Verification: Integrations with HiveOS, BraiinsOS, CGMiner, Minerstat, F2Pool, ViaBTC, and Antpool.
* Data Points: Hashrate, uptime percentage, temperature, and payout frequency.
* Data Privacy: Only non-sensitive operational metrics are shared publicly.
* Manual + API Audits: Each listing undergoes both automated verification and human review to eliminate fake rigs.
* Custom Integrations: Available for proprietary software via API adapters.


---

# 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/earnings-fees-and-payout-mode.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.