> For the complete documentation index, see [llms.txt](https://hugs-solutions.gitbook.io/hugs-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hugs-solutions.gitbook.io/hugs-platform/the-hugs-token-usdhugs/token-allocation.md).

# Token Allocation

## Community focussed

Up to 25% of the total supply of $HUGS will be sold during the token sale, and a minimum of 25% of the total supply is reserved for the Hugs Limited operations and its team.

45% of the $HUGS supply will be reserved to bootstrap the Curator ecosystem, of which a large part will be poured into the elastic reward pool. 

## Token allocation table 

| **Destination**                    | **$HUGS (M)** | **Percentage** |
| ---------------------------------- | ------------- | -------------- |
| **Token sale**                     | **25**        | **25 %**       |
| *Early Supporters*                 | 4             | 4*%*      |
| *Private Sale*                     | 6             | 6*%*      |
| *Public sale*                      | 1*5*          | 1*5%*          |
| **Hugs Ltd**                       | **30**        | **30 %**       |
| *Development*                      | *5*           | *5 %*          |
| *Partnerships*                     | *2*           | *2 %*          |
| *Marketing*                        | *3*           | *3 %*          |
| *Team & Advisors*                  | 10            | 10 *%*         |
| Exchange liquidity                 | 10            | 10%            |
| **Community incentives & rewards** | **45**        | **45 %**       |
| **TOTAL SUPPLY**                   | **100**       | **100 %**      |

### Token allocation explained

#### **Token sale**

The initial number of tokens sold to early investors. The proceeds of this token sale will be used by the Hugs team to cover design, market research, R\&D of the Platform, team growth, and operational costs.

#### **Development**

These tokens are reserved to cover additional costs for the development of our platform and proof of concepts.

#### **Partnerships**

Various partnerships will be established. Some partnerships require an investment in time and material. A number of tokens have been reserved to cover this.

#### **Marketing**

As is common practice in crypto and blockchain projects, Hugs will build a community of supporters. This includes affiliates, contributors, testers, etc. Valuable contributions can be rewarded with tokens.

#### **Team & Advisors**

Preceding the launch of the $HUGS token, a number of enthusiasts and advisors have voluntarily contributed to the project. They will be rewarded with tokens for their time, expertise, and effort.

#### Exchange liquidity

Listing a token on an exchange requires a number of tokens to be provided for market-making purposes, to ensure that buy and sell orders can take place with the smallest possible delay.

#### **Community incentives & rewards**

The goal is to provide funding for community initiatives focussing on community-driven solutions willing to build on top of Curator and to use $HUGS in our Elastic Reward Pool.


---

# 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://hugs-solutions.gitbook.io/hugs-platform/the-hugs-token-usdhugs/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.