> 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/tokenomics.md). # Tokenomics ## $HAVL Tokenomics $HAVL is designed to align the growth of havl with the humans, developers and organizations that participate in the network. The token distribution prioritizes broad public ownership, long-term ecosystem incentives and transparent capital formation. There is **no direct founder token allocation**. ### Token Distribution
AllocationTokensShare
Fair Launch435,000,00043.5%
Community Airdrop40,000,0004.0%
Virtuals Ecosystem Airdrop25,000,0002.5%
Automated Capital Formation250,000,00025.0%
havl Ecosystem150,000,00015.0%
Protocol Burn100,000,00010.0%
Total1,000,000,000100%
At a high level: **50%** — Public & Community\ **25%** — Automated Capital Formation\ **15%** — havl Ecosystem\ **10%** — Protocol Burn *** ### 43.5% — Fair Launch **435,000,000 $HAVL** The largest allocation of $HAVL is distributed through the public launch on Virtuals. There is no private token sale or separate founder allocation. The Fair Launch establishes the initial market for $HAVL and makes public distribution the largest individual component of the token supply. *** ### 4% — Community Airdrop **40,000,000 $HAVL** 4% is reserved for the early havl community. The allocation is acquired through the launch mechanism and distributed to eligible early supporters and contributors. Eligibility criteria, snapshots and claim details will be announced separately. The allocation will be held in publicly identifiable wallets wherever technically possible, allowing the distribution to be verified on-chain. *** ### 2.5% — Virtuals Ecosystem Airdrop **25,000,000 $HAVL** 2.5% is distributed through the Virtuals ecosystem as part of the $HAVL launch. This creates initial distribution among participants in the broader Virtuals ecosystem and follows the applicable Virtuals launch mechanics. *** ### 25% — Automated Capital Formation **250,000,000 $HAVL** 25% is allocated to **Automated Capital Formation (ACF)**. ACF provides funding for the continued development of havl without requiring a traditional private token round. The allocation follows Virtuals' **Limit Order Program**, progressively releasing tokens at predefined valuation milestones between approximately **$2 million and $160 million FDV**. Capital generated through ACF can be used to finance product development, infrastructure, network expansion, integrations, operations and the broader growth of havl. ACF is therefore a **company financing mechanism — not a direct founder token allocation**. *** ### 15% — havl Ecosystem **150,000,000 $HAVL** 15% is reserved for the long-term growth of the havl network. The allocation supports areas such as: * Verifier rewards and network incentives * Certified Expert programs * Developer grants and integrations * Ecosystem partnerships * Network growth initiatives #### Vesting The full ecosystem allocation is locked at launch and released gradually over **48 months**. **6-month cliff**\ No ecosystem tokens are released during the first six months. **42-month linear vesting**\ Following the cliff, the allocation unlocks progressively over the remaining 42 months. This prevents a large ecosystem reserve from entering circulation immediately and aligns token distribution with the actual development of the network. As havl matures, the objective is for verifier compensation to become increasingly supported by real verification demand and network revenue rather than token emissions alone. *** ### 10% — Protocol Burn **100,000,000 $HAVL** 10% of the initial supply is permanently designated for burn. The allocation is locked at launch and follows a predefined vesting schedule. **Every token released from this allocation is burned rather than entering circulation.** #### Burn Schedule The Protocol Burn follows a **48-month schedule**: **6-month cliff**\ The entire 100 million $HAVL allocation remains locked. **42-month linear release and burn**\ After the cliff, tokens unlock progressively. Every unlocked token is automatically or verifiably sent to the designated burn address. The allocation can therefore never be used by havl, founders or ecosystem participants. Once the complete burn schedule has concluded, the effective maximum supply will have been reduced from: **1,000,000,000 → 900,000,000 $HAVL** All burn transactions will be publicly verifiable on-chain. ### Built for the Network $HAVL separates **public ownership, company financing and network incentives**. **50%** is allocated to public and community distribution.\ **25%** provides milestone-based capital for building havl.\ **15%** supports the long-term growth of the human verification network.\ **10%** is permanently removed from supply. The result is a token structure designed around the long-term development of the havl network rather than short-term insider ownership. **Machines act. Humans verify.** {% hint style="warning" %} These percentages represent the current design and may change before the token launch. They are not an offer, guarantee, or investment recommendation. {% 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/tokenomics.md?ask=&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.