> For the complete documentation index, see [llms.txt](https://docs.honey.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.honey.fun/usdaibera/token-distribution.md).

# Token Distribution

<figure><img src="/files/G8GtyL0uU6faQ3dx4nZR" alt=""><figcaption></figcaption></figure>

When raising our funding rounds, we had one clear goal: to bring together investors **who truly understand our needs and can actively help us grow**. The funds we’ve raised have enabled us to build cutting-edge technology, assemble a promising team, and secure the financial support needed for our future growth.

**Token Distribution:**\
**Total supply: 100,000,000**

* **Pre-seed**: 20% of total supply – 15% TGE, 2-month cliff, 6-month linear
* **Seed**: 17.19% of total supply – 17.5% TGE, 2-month cliff, 4-month linear
* **Public**: 13.87% of total supply – 35% TGE, 1-month cliff, 3-month linear
* **Strategic Partnerships**: 10% of total supply – 35% TGE, 4-month linear
* **Airdrop**: 5% of total supply – 50% TGE, 6-month linear
* **Liquidity**: 18% of total supply – vesting depends on market/listing needs
* **Development & Ecosystem**: 15.95% of total supply – 6-month linear

Our vesting schedules are short and dynamic, with significant early unlocks. We believe long vesting periods can be detrimental to protocols. While the initial inflation might seem high, it will quickly taper off, allowing us to **gain traction fast** and draw attention not only within **Berachain** but also across the broader crypto space. This positions us for **long-term growth** and success.


---

# 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.honey.fun/usdaibera/token-distribution.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.