> 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/the-hello-economy.md). # The Hello Economy The Hello Economy is the planned economic layer connecting Hello.Fun platform activity, $HELLO and selected tokens launched through the ecosystem. The model is designed around a simple principle: **Value generated by the platform should flow back into the ecosystem.** ### The Economic Model The planned model allocates **100% of Hello.Fun platform revenue** back into the ecosystem through market buybacks. The proposed allocation is: | Allocation | Share of Platform Revenue | | ---------------------------------- | ------------------------: | | $HELLO Market Buybacks | 60% | | Selected Hello.Fun Launch Buybacks | 40% | | **Total** | **100%** | ```mermaid flowchart TD A["Hello.Fun Platform Revenue"] --> B["100% Ecosystem Allocation"] B --> C["60%"] B --> D["40%"] C --> E["$HELLO Market Buybacks"] D --> F["Selected Launch Buybacks"] ``` This model is part of the planned Hello Economy and is not active within the currently deployed Hello.Fun system. ### The $HELLO Side Under the planned model, **60% of platform revenue** is allocated to market buybacks of $HELLO. The $HELLO acquired through these buybacks is intended to be permanently removed from supply through burning. ```mermaid flowchart LR A["60% of Platform Revenue"] --> B["$HELLO Market Buybacks"] B --> C["$HELLO Purchased"] C --> D["Burn"] D --> E["Removed From Supply"] ``` This creates the planned connection between Hello.Fun platform activity and $HELLO. ### The Launch Side The remaining **40% of platform revenue** is planned for market buybacks of selected tokens launched through Hello.Fun. ```mermaid flowchart LR A["40% of Platform Revenue"] --> B["Launch Buyback Allocation"] B --> C["Selected Hello.Fun Tokens"] C --> D["Market Buybacks"] ``` This side of the model is designed to extend the economic loop beyond $HELLO and into the wider launch ecosystem. Not every launch is intended to receive these buybacks. Projects would need to be selected under the Hello Economy's project selection framework. ### Connecting the Platform and Its Launches The Hello Economy is designed to create a relationship between activity on Hello.Fun and the markets growing through it. ```mermaid flowchart TD A["Hello.Fun Activity"] --> B["Platform Revenue"] B --> C["Hello Economy"] C --> D["$HELLO Buybacks"] C --> E["Selected Launch Buybacks"] D --> F["$HELLO Ecosystem"] E --> G["Hello.Fun Launch Ecosystem"] ``` This creates two planned paths for platform generated value. One connects back to $HELLO. The other connects back to selected launches. ### Platform Revenue Platform revenue refers to revenue generated through the Hello.Fun protocol. The currently deployed platform can generate protocol revenue through trading activity. The Hello Economy is intended to add a future allocation layer that determines how platform revenue is used within the broader ecosystem. ```mermaid flowchart LR A["Platform Activity"] --> B["Platform Revenue"] B --> C["Hello Economy"] C --> D["Ecosystem Allocation"] ``` The current protocol fee system and the planned Hello Economy should therefore be understood as separate layers. The fee system generates protocol revenue. The Hello Economy defines the planned use of that revenue. ### A Broader Ecosystem Loop The planned model is designed to create a recurring relationship between platform usage and ecosystem activity. ```mermaid flowchart TD A["More Platform Activity"] --> B["Platform Revenue"] B --> C["Market Buybacks"] C --> D["$HELLO"] C --> E["Selected Launches"] D --> F["Hello.Fun Ecosystem"] E --> F F --> A ``` The purpose is to make the economics of Hello.Fun extend beyond collecting platform fees. ### Buybacks Are Market Purchases The planned buyback model uses market buybacks. That means tokens would be acquired through their markets rather than being taken directly from creator or user balances. For $HELLO, purchased tokens are intended to be burned. For selected Hello.Fun launches, the separate Launch Buyback model determines how the ecosystem allocation is directed. ### Selection Matters The 40% Launch Buyback allocation is intended for selected projects rather than automatically being distributed across every token launched through Hello.Fun. ### Selection Matters The 40% Launch Buyback allocation is intended for selected projects rather than automatically being distributed across every token launched through Hello.Fun. The planned selection framework considers factors such as: 1. Volume 2. Holders 3. Bubblemaps 4. Tokenomics 5. Team 6. Market Cap The detailed selection model is covered in **Project Selection**. ### Current Status The Hello Economy represents the planned economic direction of the ecosystem. The currently deployed Hello.Fun protocol does not yet execute: 1. The 60% $HELLO buyback allocation 2. The 40% Launch Buyback allocation 3. $HELLO burns 4. Automated project selection These mechanisms will require their respective ecosystem components before the full economic model becomes active. ### One Platform, Two Sides of the Economy The Hello Economy is designed to support both the platform token and the ecosystem being built around it. **60% → $HELLO** **40% → Selected Hello.Fun Launches** ```mermaid flowchart LR A["Hello.Fun Grows"] --> B["Hello Economy"] B --> C["$HELLO"] B --> D["Selected Launches"] ``` Hello.Fun is designed not only to create markets. The Hello Economy is designed to connect platform growth back to the markets growing with it. --- # 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/the-hello-economy.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.