> For the complete documentation index, see [llms.txt](https://humb-io.gitbook.io/humb.io-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humb-io.gitbook.io/humb.io-docs/h2p-token.md). # H2P Token ### Token Utility H2P powers the HUMB ecosystem, and trading, listings, and rewards on the platform all run through it. **Primary Functions** | Function | Description | | ----------------------- | -------------------------------------------------------------------------------------------- | | Trading Pair | All healthcare tokens pair with H2P, making it the base for every healthcare token trade | | Fee Payment | Pay trading fees in H2P for discounts based on your tier | | Ecosystem Participation | Hold H2P and actively participate to access ecosystem benefits and the Community Growth Pool | | Launchpad Access | Use H2P to participate in new healthcare token launches | | Healthcare Payments | Use H2P as payment for healthcare consultations, wellness services, and care packages | | Governance | Vote on platform decisions, feature priorities, and ecosystem fund allocation | **Supply Overview** | Metric | Value | | --------------------------------- | ------------------------------- | | Initial Total Supply | 100,000,000 H2P | | Token Standard | ERC-20 on Ethereum | | Initial Listing Price | To be announced | | Launch Market Cap | To be announced | | Circulating Supply at TGE (Day 1) | 21,500,000 H2P (21.5% of total) | | Long Term Supply Target | 50,000,000 H2P | **Tokenomics and Distribution** | Category | Allocation | Tokens | Purpose | | ----------------------- | ---------- | --------------- | ----------------------------------------------------------------------- | | Ecosystem and Community | 30% | 30,000,000 | Participation incentives, staking rewards, community programs | | Team and Advisors | 15% | 15,000,000 | Core team and strategic advisors, vested | | Liquidity Reserve | 15% | 15,000,000 | Exchange liquidity, managed by treasury | | Platform Growth | 15% | 15,000,000 | Marketing, partnerships, user acquisition | | Token Sales | 15% | 15,000,000 | Private round, public presale and launchpad sale, with a locked reserve | | Treasury | 10% | 10,000,000 | Multisig held, board governed | | **Total** | **100%** | **100,000,000** | | **Token Sales** | Token Sales group | Tokens | | ----------------- | -------------- | | Private round | 5,000,000 | | Public presale | 5,000,000 | | Launchpad sale | 3,000,000 | | Locked reserve | 2,000,000 | | **Total** | **15,000,000** | Unsold tokens from any round return to the locked reserve. **Token Unlock Schedule** At TGE (Day 1), the following portions of each allocation enter circulation: | Allocation | Unlocked at TGE | Tokens | | -------------------------------------------- | --------------- | -------------- | | Liquidity Reserve | 60% | 9,000,000 | | Ecosystem and Community (initial activation) | 25% | 7,500,000 | | Platform Growth (initial release) | 16% | 2,400,000 | | Token Sales buyers | 14% | 2,100,000 | | Treasury (initial working capital) | 5% | 500,000 | | **Total Circulating at Launch** | | **21,500,000** | Private round buyers receive 10% of their tokens at TGE, and presale and launchpad buyers receive 20%, with the rest released in equal monthly amounts over 12 months. Team and Advisors receive nothing at TGE, and their tokens stay locked for 12 months before being released monthly over 36 months. The 21,500,000 launch circulating supply is fixed. As vesting releases happen in the years following TGE, additional tokens enter circulation according to these schedules, balanced against the structured burn program described below. **Burn Mechanism** As vesting releases more tokens into circulation, HUMB runs a structured burn program alongside it so that the growth in supply is offset over time, followed by a permanent fee-based burn from the sixth year onward. **Structured Burn Program (Years 1 to 5)** Burns happen three times per year, every four months, sourced from the Platform Growth, Ecosystem, and Community allocation pools. Each burn is executed automatically by a smart contract on a predetermined schedule and is publicly verifiable on-chain. | Year | Burn Events | Tokens Burned | | --------- | ------------- | -------------------- | | Year 1 | 3 | 1,500,000 | | Year 2 | 3 | 1,200,000 | | Year 3 | 3 | 900,000 | | Year 4 | 3 | 700,000 | | Year 5 | 3 | 500,000 | | **Total** | **15 events** | **4,800,000 burned** | **Perpetual Fee-Based Burns (After Year 5)** Once the structured program concludes, HUMB will activate a permanent deflationary mechanism. 1% of all trading fees collected on the platform will be used to repurchase H2P from the open market, and the bought-back tokens are burned quarterly. The exact buyback percentage will be governed by H2P token holders via an on-chain vote, subject to a minimum floor established at TGE. Burns continue indefinitely, creating a permanent reduction in supply. Because the buyback mechanism is funded by platform trading fees, the speed of burns reflects actual platform activity, so higher trading volume means faster burns and lower volume means slower burns. **Long-Term Supply Target: 50,000,000 H2P** HUMB targets a long-term final supply of 50,000,000 H2P, achieved through the combination of the structured five-year burn program and the perpetual fee-based burns thereafter. This is a directional target without a fixed timeline because fee-based burns scale with platform trading volume. --- # 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://humb-io.gitbook.io/humb.io-docs/h2p-token.md?ask=&goal= ``` `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.