> 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/system-architecture-and-how-it-works.md).

# System Architecture and How It Works

The platform is designed to provide a seamless and trust-minimised experience for all users.

**User Journeys:**\ <br>

<figure><img src="https://676732118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOmI7YH9L04aQwYYwUxxt%2Fuploads%2FwnwxST8L4W8UowiHJYkj%2Fimage.png?alt=media&amp;token=ebecb6ce-249b-4578-bfb1-0ac631b0760f" alt=""><figcaption></figcaption></figure>

**Funds and Data Flow:**

<figure><img src="https://676732118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOmI7YH9L04aQwYYwUxxt%2Fuploads%2FgpjJdrHsFyh2dd8d7AbH%2Fpicture%204.png?alt=media&amp;token=698a594d-2e95-4d8a-9134-8a332e43e558" alt=""><figcaption></figcaption></figure>

1. Primary Raise: An investor pays in $ROGZ to the PrimaryOffering smart contract. A PaymentSplitter contract automatically directs 97% of the funds to the operator's Special Purpose Vehicle (SPV) and 3% to the Protocol Treasury. ShareVault NFTs are then minted to the investor.
2. Mining Operations: The SPV manages the physical mining operations, with mining pool payouts directed to an SpvCashbox contract.
3. Reward Settlement: The SPV reports the rewards earned via the RewardRouter contract.
4. Reward Distribution: A MerkleDistributor contract enables investors to claim their pro-rata share of rewards in $ROGZ in a gas-efficient manner.
5. Secondary Trading: The SecondaryMarketplace contract facilitates peer-to-peer trading of share NFTs, with a 1% fee directed to the Treasury.<br>

**How RigWorkZ Works**

**Operator Onboarding:**\
Operators register, complete KYC/AML verification via partners such as Sumsub, and provide facility details and rig specifications. Each operator signs a non-exclusive digital listing agreement, retaining full ownership of their hardware.

**Rig Verification:**\
Operators connect their rigs using RigWorkZ’s unified verification layer compatible with HiveOS, BraiinsOS, CGMiner, Minerstat, F2Pool, Antpool, and other major mining software and pools. RigWorkZ automatically aggregates real-time data such as uptime, temperature, hashrate, and pool performance, cross-verifying it through multiple APIs to prevent falsification.

**Bonding (Proof of Integrity):**\
Instead of paying traditional listing fees, operators post refundable $ROGZ bonds as proof of reliability. Bond ratios determine listing visibility and capital access, creating a transparent, performance-based reputation system.

**Capital Raise via NFTs:**\
Verified rigs are fractionalized into NFT-backed shares. Investors purchase these NFTs using USDC, USDT, or $ROGZ. The raised capital is held in escrow and released to the operator’s SPV account only after full verification, typically within 90 days.

**Reward Distribution:**\
Mining rewards flow to a rewards escrow smart contract and are distributed automatically to NFT holders in $ROGZ. Operators receive 97% of verified rewards, while the platform retains a 3% performance fee for automation, verification, and compliance.

**Delisting or Exit:**\
Operators can delist rigs after each investor cycle or repurchase outstanding NFTs to regain 100% of their allocation.<br>

<mark style="color:$info;">Legal Integration via Special Purpose Vehicles (SPVs): To bridge the on-chain and off-chain worlds, legal compliance and asset ownership are managed through SPVs. Each on-chain listing is legally tied to a specific SPV, with contracts like SpvRegistrar and DocsRegistry binding the digital asset to the legal entity and storing relevant documentation hashes on IPFS/Arweave.</mark>

<br>


---

# 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/system-architecture-and-how-it-works.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.