> For the complete documentation index, see [llms.txt](https://docs.hashcloud.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashcloud.sh/vip-amplify/vip-gpu-limits-and-hardware-tiering.md).

# VIP GPU Limits & Hardware Tiering

### **Overview**

To preserve decentralization and maintain hardware fairness, HashCloud enforces structured GPU and VRAM limits across its VIP tiers. This policy ensures that no miner can dominate the network using industrial-scale rigs or ultra-high-end GPUs, while still rewarding legitimate contributors who stake tokens and participate actively in the ecosystem.

The **Hardware Tiering Model** establishes a clear set of boundaries defining how many GPUs a miner may operate and the maximum VRAM capacity per GPU, aligned with their VIP staking level. This approach promotes equitable access, competitive mining conditions, and broad participation among consumer-grade hardware owners.

### VIP Hardware Rules

Each VIP tier defines both the **GPU count allowance** and **maximum VRAM capacity per GPU**. These parameters are validated on registration and continuously enforced by backend verification to prevent tier violations.

| VIP Level | GPUs Allowed | Max VRAM per GPU | Example Hardware     |
| --------- | ------------ | ---------------- | -------------------- |
| Free      | 1            | 6 GB             | GTX 1060-RX 580      |
| VIP1      | 2            | 8 GB             | RTX 3050-1660 Super  |
| VIP2      | 4            | 12 GB            | RTX 3060–4070        |
| VIP3      | 8            | 24 GB            | RTX 4090-A100, MI300 |

### **Design Philosophy**

The VIP hardware tiering structure is guided by three core design principles:

1. **Hardware Neutrality** – HashCloud promotes accessibility for consumer and mid-range GPUs while still allowing scalability through higher staking tiers.
2. **Anti-Centralization** – Restricting VRAM-heavy hardware mitigates the risk of data center monopolization, preserving decentralized ownership.
3. **Competitive Parity** – The system’s tier scaling ensures that smaller miners remain competitive within their category, reinforcing network diversity.

### **Purpose and Network Impact**

#### **Key Objectives**

* **Limit GPU Dominance:** Prevent high-VRAM data-center GPUs from overpowering retail miners.
* **Preserve Decentralization:** Avoid concentration of mining power in large corporate or industrial setups.
* **Enhance Fairness:** Create a balanced environment where consumer-grade GPUs remain viable participants.

#### **Positive Outcomes**

* Maintains consistent **reward equilibrium** across diverse hardware sets.
* Protects the network from **hardware-based manipulation** or **tier spoofing**.
* Encourages sustainable decentralization by keeping participation open to a broad range of miners globally.

### **Enforcement and Validation System**

The HashCloud backend enforces tier compliance through an automated, tamper-resistant hardware validation framework.

#### **Validation Process Flow**

```
GPU Registration → UUID Verification → VRAM Check → Tier Match → Authorization Granted
```

#### **Mechanics**

* **GPU UUID Validation:** Each GPU is uniquely identified and bound to the miner’s node ID.
* **VRAM Limit Enforcement:** The system automatically compares VRAM specs against the tier allowance.
* **Backend Rejection:** Configurations exceeding limits are rejected with logged reports and penalties for repeated violations.

This ensures hardware transparency and eliminates unfair advantages, allowing equitable access to compute rewards.

### **Future Considerations**

As GPU technology continues to evolve, HCLD’s governance may update tier thresholds to reflect market trends and hardware availability. Future proposals may include:

* Support for multi-tenant or cloud-based GPU leasing under regulated staking conditions.
* Expansion of upper-tier VRAM limits for AI-specialized GPUs.
* Dynamic tier calibration based on network compute distribution.

Through periodic review and community consensus, HashCloud ensures that the **Hardware Tiering Policy** remains fair, relevant, and adaptive to technological progression.


---

# 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:

```
GET https://docs.hashcloud.sh/vip-amplify/vip-gpu-limits-and-hardware-tiering.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.