> For the complete documentation index, see [llms.txt](https://docs.havl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.havl.io/usdhavl-and-network-economics/genesis-community-airdrop.md).

# Genesis Community Airdrop

The Genesis Community Airdrop is intended to recognize and seed the early havl community.

The current tokenomics reserve **10% of total $HAVL supply** for the community airdrop, with the allocation planned in two equal phases: half at launch and half at a later distribution.

Community qualification can include early participation signals such as joining the waitlist and connecting an X account. The final eligibility rules, snapshot logic, anti-sybil measures, and claim process will be announced separately.

{% hint style="warning" %}
Never trust unofficial claim links or requests for seed phrases. Official eligibility and claim instructions will only be published through havl-controlled channels.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.havl.io/usdhavl-and-network-economics/genesis-community-airdrop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.