> For the complete documentation index, see [llms.txt](https://hash-network-1.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://hash-network-1.gitbook.io/docs/tokenomics/token-allocation.md).

# Token Allocation

### **Token Allocation**

The total supply of **1,000,000,000 HASH** is distributed as follows:

<table><thead><tr><th width="197">Category</th><th width="114">Allocation</th><th width="121">Amount</th><th width="348">Vesting &#x26; Lock Mechanism</th></tr></thead><tbody><tr><td><strong>Mining Rewards</strong></td><td>40%</td><td>400M HASH</td><td>Unlock 100% at TGE</td></tr><tr><td><strong>Ecosystem &#x26; Growth</strong></td><td>15%</td><td>150M HASH</td><td><p>TGE: 5%</p><p>Vesting: Linear over 36 months</p></td></tr><tr><td><strong>Treasury</strong></td><td>15%</td><td>150M HASH</td><td>TGE: 0% | Cliff: 6 months
<br>Vesting: Linear over 48 months</td></tr><tr><td><strong>Team</strong></td><td>10%</td><td>100M HASH</td><td>TGE: 0% | Cliff: 12 months
<br>Vesting: Linear over 36 months</td></tr><tr><td><strong>Investors</strong></td><td>5%</td><td>50M HASH</td><td>TGE: 10% | Cliff: 3 months
<br>Vesting: Linear over 18–24 months</td></tr><tr><td><strong>Liquidity (DEX &#x26; CEX)</strong></td><td>10%</td><td>100M HASH</td><td>TGE: 100% (locked in liquidity pools)
<br>LP tokens: Locked via smart contract &#x26; permanently locked</td></tr><tr><td><strong>Marketing / KOL</strong></td><td>5%</td><td>50M HASH</td><td>TGE: 5%
<br>Vesting: Linear over 12–18 months</td></tr></tbody></table>

***

### **Allocation Breakdown**

#### **1. Mining Rewards (40%)**

This is the largest allocation, dedicated to incentivizing users participating in the network. The network grows as its community grows.

* Distributed to miners based on activity and contribution
* Supports long-term engagement and ecosystem growth
* Ensures fair and decentralized reward distribution

***

#### **2. Ecosystem & Growth (15%)**

Allocated to expand the Hash Network ecosystem.

* Partnerships and integrations
* Development of new features and products
* Incentives for developers and collaborators

***

#### **3. Treasury (15%)**

Reserved for long-term sustainability and strategic initiatives.

* Emergency funding
* Protocol upgrades
* DAO-controlled future investments

***

#### **4. Team (10%)**

Allocated to core contributors and builders of Hash Network.

* Subject to vesting schedules to ensure long-term commitment
* Aligns team incentives with project success

***

#### **5. Investors (5%)**

Distributed to early supporters and strategic investors.

* Provides initial capital for development and scaling
* Typically subject to lock-up and vesting conditions

***

#### **6. Liquidity (DEX & CEX) (10%)**

Ensures healthy market activity and accessibility.

* Provides liquidity for trading pairs
* Supports listings on decentralized and centralized exchanges
* Reduces price volatility

***

#### **7. Marketing / KOL (5%)**

Dedicated to user acquisition and brand growth.

* Influencer partnerships
* Campaigns and promotions
* Community expansion initiatives


---

# 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://hash-network-1.gitbook.io/docs/tokenomics/token-allocation.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.