> 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.md).

# Tokenomics

### **Overview**

The HCLD **Token** lies at the core of the HashCloud ecosystem, functioning as the primary economic driver for compute-based participation.\
Its design emphasizes *sustainability*, *fair distribution*, and *utility alignment* ensuring that token value is directly linked to the verifiable compute output of the network rather than speculative behavior or centralized control.

HCLD’s emission and allocation frameworks are structured to support long-term network growth, stable liquidity, and consistent miner rewards while maintaining a capped supply and deflation-resistant economic model.

### **Token Allocation**

To balance growth incentives and operational resilience, HCLD’s total supply is distributed across five key categories. Each category supports a distinct function within the ecosystem, ensuring fair access, liquidity, and governance sustainability.

| **Category**                                    | **Amount (**&#x48;CL&#x44;**)** | **Percentage** | **Purpose**                                                                                                                                           |
| ----------------------------------------------- | ------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Public Sale (Initial Liquidity)**             | 10,000,000                      | 10%            | Provides initial liquidity for decentralized and centralized exchange listings, supporting token accessibility and early ecosystem adoption.          |
| **Treasury (Ecosystem, CEX Pool, Maintenance)** | 15,000,000                      | 15%            | Reserved for ecosystem maintenance, exchange partnerships, operational reserves, and strategic infrastructure expansion.                              |
|                                                 |                                 |                |                                                                                                                                                       |
|                                                 |                                 |                |                                                                                                                                                       |
| **Team/Developer Funds**                        | 10,000,000                      | 10%            | Reserved for founding developers, advisors, and future contributors. Subject to vesting schedules to ensure long-term alignment with network success. |

### **Total Supply**

Total Supply=100,000,000 HCLD

The total HCLD supply is permanently capped at **100 million tokens**, ensuring a fixed emission ceiling. No additional tokens will ever be minted beyond this cap, preserving scarcity and protecting tokenholder value.

### **Emission Model**

The **Mining Pool** representing 60% of total supply is structured for gradual daily emissions distributed through the Proof-of-Compute reward mechanism. This ensures a sustainable and predictable release schedule that encourages active network participation.

#### **Emission Characteristics**

* **Daily Reward Rate:** Derived from verified compute output normalized by network difficulty.
* **Dynamic Scaling:** Adjusts emission pacing in proportion to active miner participation and VIP multiplier averages.
* **Longevity-Oriented Distribution:** Designed to sustain emissions across multiple years, promoting stable network growth and consistent participation rewards.

This model effectively transforms the mining pool into a *self-regulating economic engine* that incentivizes both compute contribution and staking commitment.

### **Economic Objectives**

HCLD’s tokenomics model was built to achieve five foundational economic goals:

1. **Sustainable Growth:** Maintain balance between reward attractiveness and emission longevity.
2. **Fair Distribution:** Ensure that early adopters, long-term miners, and ecosystem participants receive proportional value.
3. **Liquidity Accessibility:** Support healthy trading volumes and network expansion through public sale and treasury reserves.
4. **Deflation Control:** Avoid inflationary drift by strictly capping supply and preventing mint-based staking yield.
5. **Network Utility Integration:** Ensure the HCLD token remains a critical utility within compute verification, staking, and governance processes.

### **Token Flow Summary**

#### **Simplified Flow Representation**

```
Total Supply (100M HCLD)
    ↓
  Distribution Pools
    ↓
  Mining Pool → Daily Emission → Verified Miners
  Treasury → Operations, Ecosystem Growth
  Public Sale → Liquidity and Accessibility
  Early Reward → Community Incentives
  Team/Dev → Long-Term Development
```

{% hint style="info" %}
Mining pool emissions are released daily to ensure long-term network participation and reward fairness.
{% endhint %}


---

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