> For the complete documentation index, see [llms.txt](https://hello-fun-1.gitbook.io/hello.fun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello-fun-1.gitbook.io/hello.fun-docs/tokenomics.md). # Tokenomics $HELLO is designed as the ecosystem token of Hello.Fun. Its planned tokenomics combine a fixed supply with allocations for liquidity, creator and ecosystem rewards, community growth, treasury and team participation. ### Total Supply The planned total supply is: **1,000,000,000 $HELLO** The tokenomics are based on this fixed supply. ### Token Allocation | Allocation | Share | $HELLO | | ----------------------------- | -------: | ----------------: | | Liquidity | 45% | 450,000,000 | | Creator and Ecosystem Rewards | 25% | 250,000,000 | | Community and Growth | 15% | 150,000,000 | | Treasury | 10% | 100,000,000 | | Team | 5% | 50,000,000 | | **Total** | **100%** | **1,000,000,000** | ```mermaid pie showData title $HELLO Token Allocation "Liquidity" : 45 "Creator and Ecosystem Rewards" : 25 "Community and Growth" : 15 "Treasury" : 10 "Team" : 5 ``` ### Liquidity **45% of the planned supply** **450,000,000 $HELLO** The largest allocation is designated for liquidity. This allocation is intended to support liquidity requirements around $HELLO as the token becomes part of the broader Hello.Fun ecosystem. ### Creator and Ecosystem Rewards **25% of the planned supply** **250,000,000 $HELLO** This allocation is intended for creator and ecosystem rewards. Hello.Fun is designed around creators launching markets, making creator participation an important part of the planned $HELLO ecosystem. This allocation can support the broader incentive structure as $HELLO utility expands. ### Community and Growth **15% of the planned supply** **150,000,000 $HELLO** The Community and Growth allocation is intended to support expansion of the Hello.Fun ecosystem. This provides an allocation for initiatives focused on participation, awareness and ecosystem growth. ### Treasury **10% of the planned supply** **100,000,000 $HELLO** The Treasury allocation is intended to support the broader development and operation of the Hello.Fun ecosystem. ### Team **5% of the planned supply** **50,000,000 $HELLO** The Team allocation represents 5% of the planned total $HELLO supply. ### Allocation Overview ```mermaid flowchart TD A["1,000,000,000 $HELLO"] --> B["45% Liquidity"] A --> C["25% Creator and Ecosystem Rewards"] A --> D["15% Community and Growth"] A --> E["10% Treasury"] A --> F["5% Team"] ``` The allocation places **85% of the planned supply** across liquidity, creator and ecosystem rewards, and community and growth. The remaining **15%** is allocated between treasury and team. ### $HELLO and Pairing One of the planned utilities for $HELLO is its use as a Hello.Fun pairing asset. As pair choice expands, creators will be able to build markets around supported assets rather than relying on a single pairing option. $HELLO is intended to become part of that system. ```mermaid flowchart LR A["$HELLO"] --> B["Pairing Asset"] B --> C["New Hello.Fun Launch"] C --> D["$HELLO Pair Market"] ``` This gives $HELLO a planned functional role within the launch experience itself. ### $HELLO and Creator Incentives $HELLO pairing is also designed to connect with **Enhanced Creator Rewards**. These incentives form part of the planned $HELLO ecosystem and are intended to create additional reasons for creators to choose $HELLO when launching a market. ### $HELLO and the Hello Economy The planned Hello Economy creates another connection between $HELLO and Hello.Fun platform activity. Under the proposed model: **60% of platform revenue → $HELLO Market Buybacks and Burn** **40% of platform revenue → Selected Hello.Fun Launch Buybacks** ```mermaid flowchart TD A["Hello.Fun Platform Revenue"] --> B["60%"] A --> C["40%"] B --> D["$HELLO Market Buybacks"] D --> E["Burn"] C --> F["Selected Launch Buybacks"] ``` This economic model is planned and is not currently active within the deployed Hello.Fun protocol. ### Buyback and Burn $HELLO acquired through the planned 60% market buyback allocation is intended to be burned. ```mermaid flowchart LR A["Platform Revenue"] --> B["$HELLO Market Buyback"] B --> C["Purchased $HELLO"] C --> D["Burn"] D --> E["Permanently Removed From Supply"] ``` This mechanism is designed to permanently remove bought back $HELLO from supply once the Hello Economy becomes active. ### Current Status The $HELLO token and its associated ecosystem mechanics are part of the planned expansion of Hello.Fun. The currently deployed Hello.Fun platform does not yet use $HELLO as a pairing asset and does not currently operate the planned buyback and burn mechanism. The tokenomics on this page describe the planned $HELLO ecosystem structure. ### The $HELLO Ecosystem The planned role of $HELLO brings together several parts of Hello.Fun. ```mermaid flowchart TD A["$HELLO"] --> B["Pairing"] A --> C["Creator Incentives"] A --> D["Hello Economy"] A --> E["Ecosystem Growth"] D --> F["Market Buybacks"] F --> G["Burn"] ``` **Fixed supply. Pairing utility. Creator incentives. Ecosystem economics.** $HELLO is designed to become part of how the Hello.Fun ecosystem launches, connects and grows. --- # 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://hello-fun-1.gitbook.io/hello.fun-docs/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.