> For the complete documentation index, see [llms.txt](https://oreon-protocol.gitbook.io/oreonhash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oreon-protocol.gitbook.io/oreonhash-docs/oreon.md).

# OREON

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

**OREON** is a decentralized modular hashrate platform that redefines how individuals and institutions access, manage, and profit from Bitcoin mining.

It breaks away from the traditional, hardware-dependent model by enabling users to lease flexible hashrate modules without buying mining machines, managing infrastructure, or paying electricity bills. These modules generate real-time BTC income, delivered hourly and directly into the user’s wallet.

### 🛠️ Technical Framework: Two-Layer Architecture

At the core of OREON’s innovation lies a powerful two-layer architecture that brings mining into the on-chain era.

#### 🔍 1. HashDoc Intelligent Diagnostic System

**HashDoc** acts as the real-time diagnostic brain of Oreon’s mining network.

Key Functions:

* **Continuous On-Chain Scanning**: Interfaces with mining farms via hardware sensors, API access, and on-chain data feeds.
* **AI-Powered Anomaly Detection**: Uses machine learning models (e.g., **XGBoost**, **LightGBM**) to identify idle or underperforming hashrate.
* **Smart Recovery Protocols**: Triggers automated instructions to reactivate and optimize underutilized machines.
* **Performance Forecasting**: Predicts output potential to ensure profitable hashrate conversion.

Outcome:\
Mining farms can now **monetize waste computing power** that was previously unutilized.

#### 🧩 2. HashFrag Protocol Modularization & Distribution

The **HashFrag Protocol** transforms recovered computing power into tradable, programmable financial units.

Core Mechanics:

* **Modular Packaging**: Recovered hashrate is split into standardized units and wrapped into smart contracts.
* **On-Chain Rights Assignment**: Users receive ownership of these units through on-chain rights mapping.
* **Transparent Income Attribution**: Each unit is directly linked to BTC output with provable traceability.
* **Composability**: These modular units can be integrated with DeFi protocols in the future.

Outcome:\
Users gain **secure, decentralized, and precise ownership** of mining income without managing any machines.

## 🤝 Strategic Integration with ViaBTC

To ensure reliable and consistent BTC payouts, OREON integrates with ViaBTC, one of the world’s leading mining pools.

Benefits of this integration:

* **Direct Settlement**: User earnings are settled hourly and directly from ViaBTC to their wallets.
* **No Custodial Risk**: OREON doesn’t hold funds; all income flows transparently to users.
* **Proven Pool Stability**: Backed by ViaBTC’s infrastructure for uptime, accuracy, and payout reliability.

## 🌐 Why It Matters

OREON is not just a mining product it's a modular mining infrastructure protocol that transforms hashrate into a programmable financial primitive.

Key advantages:

* Open access for anyone to mine BTC without machines
* Real-time hourly payouts, no hidden fees
* Smart recovery of global waste hashrate
* Fully on-chain tracking and ownership
* Scalable design that supports future expansion into RWA and DeFi


---

# 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://oreon-protocol.gitbook.io/oreonhash-docs/oreon.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.