> 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/tokenomics/governance-and-token-utility.md).

# Governance and Token Utility

### **Decentralized Governance Model**

HashCloud (HCLD) believes that decentralization extends beyond hardware participation it must include **decision-making power**.\
Governance is designed as a **layered on-chain framework** that allows verified participants to shape network direction, protocol updates, and economic policy.

**Governance Principles**

* **Transparency:** All proposals, votes, and resolutions are recorded on-chain for verifiable public access.
* **Merit-Weighted Participation:** Both computational contribution and token holdings determine voting strength, preventing plutocracy and rewarding active miners.
* **Progressive Autonomy:** Governance begins semi-guided by the founding council and transitions into full DAO control once threshold decentralization metrics are reached.

#### **Governance Process Flow**

```
Proposal Submission → Community Discussion → Formal Vote → On-Chain Execution → Audit & Review
```

**Proposal Types**

1. **Technical Upgrades:** Protocol improvements, algorithm updates, or new compute types (e.g., ZK, AI training).
2. **Economic Adjustments:** Emission-rate tweaks, VIP tier changes, or reward redistribution.
3. **Ecosystem Growth:** Grants, partnerships, and hardware-integration initiatives.
4. **Governance Amendments:** Modifications to voting rules, quorum, or delegation mechanisms.

### **Token Utility Overview**

HCLD Tokens are not just emission rewards they are the **core fuel of participation** across mining, staking, and governance layers.

| **Utility Category**       | **Function Description**                                                                                       |
| -------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Compute Access**         | Token-based staking unlocks GPU slots and compute quotas for miners.                                           |
| **Governance Power**       | Holders can propose and vote on improvement proposals (AMPIPs).                                                |
| **Performance Multiplier** | Staked tokens increase a miner’s computation weight without generating passive yield.                          |
| **Verification Deposit**   | Certain nodes must lock HCLD to validate proofs and reduce spam submissions.                                   |
| **Ecosystem Payments**     | Used for developer bounties, integration fees, and future marketplace transactions.                            |
| **Reputation Anchor**      | Token-backed identity ensures that high-performing miners gain verifiable reputation within the HCLD registry. |

### **VIP Tier Integration and Governance Rights**

Each **VIP Tier** links staking commitment to both technical capacity and governance reach:

| **Tier**         | **Stake Requirement (**HCLD**)** | **GPU Slots**            | **Governance Vote Weight** |
| ---------------- | ------------------------------------------ | ------------------------ | -------------------------- |
| **Tier 0**       | 0 HCLD                                     | 1 GPU                    | 1×                         |
| **Tier 1**       | 1,000 HCLD                                 | 2 GPUs                   | 1.25×                      |
| **Tier 2**       | 5,000 HCLD                                 | 4 GPUs                   | 1.5×                       |
| **Tier 3**       | 10,000 HCLD                                | 8 GPUs                   | 2×                         |
| **Tier 4 (VIP)** | 25,000 HCLD + Verification Status          | 12 GPUs + priority tasks | 2.5×                       |


---

# 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://docs.hashcloud.sh/tokenomics/governance-and-token-utility.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.