> 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/key-platform-features.md).

# Key Platform Features

<figure><img src="/files/V0A7nphQNPnTXH9u5vWo" alt=""><figcaption></figcaption></figure>

**Listing & Multi-Layered Hardware Verification**

This is the cornerstone of the platform's trust model, designed to prevent data spoofing.

* Real-Time Local Verification: Operators must connect their hardware to a local verification agent. This agent communicates securely with the platform and queries the miner's software API (e.g., CGMiner on port 4028, BraiinsOS, HiveOS) to read critical stats like hashrate, power consumption, temperature, uptime, and fan speed.
* Cross-Pool API Verification: The agent's local data is cross-referenced with data from public mining pool APIs (e.g., Minerstat, SlushPool, F2Pool). This process builds a "confidence score" for each device and automatically flags inconsistencies for admin review.
* On-Chain Blockchain Verification: Custom scripts query blockchain explorers to correlate the mining pool payouts received by the operator’s registered wallet address with the verified hashrate performance, ensuring rewards are accurately reported.

**Investment & Fractional NFT Ownership**

* Tokenised Shares: Listings are divided into fractional shares, allowing investors to participate with any amount. Investors can browse and filter listings by performance, location, operator history, and other metrics.
* NFT Proof of Stake: Each share purchase mints a unique NFT (ERC-721 or ERC-1155) to the investor’s wallet, serving as an immutable, on-chain proof of their stake. NFT metadata, containing facility details and performance data, is stored decentrally on IPFS.
* Seamless Payments: All purchases are made using the $ROGZ token via integrated wallets like MetaMask, facilitated by libraries such as Web3Modal, wagmi, and ethers.js. Optional fiat-to-token on-ramps (e.g., Transak, MoonPay) are available for mainstream onboarding.

**Reward Distribution & Performance Reporting**

* Automated Payouts: Smart contracts automatically batch and distribute mining rewards to shareholders on a pro-rata basis. Rewards can be paid in their native crypto (e.g., BTC) or converted to stablecoins or $ROGZ for EVM compatibility and gas efficiency.
* Total Transparency: Investors have access to dynamic, real-time dashboards showing all hardware statistics, payout history, and rewards. All data is downloadable for tax and compliance purposes.

**Security and Compliance**

* Mandatory KYC/AML: All participants—operators and investors—must complete KYC/AML verification through integrated third-party providers like Jumio, Sumsub, or Synaps.
* Robust Security Standards: The platform enforces 2FA for operators and admins, uses salted and hashed password storage (e.g., bcrypt), and employs rate-limiting. All data is encrypted, and secrets are managed via industry-standard vaults. Smart contracts undergo full audits and include reentrancy guards and circuit breakers.
* Data Privacy: The system is designed for compliance with regulations like GDPR, featuring data minimization and consent audits.


---

# 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/key-platform-features.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.