> 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/launch-buybacks.md). # Launch Buybacks Launch Buybacks are the second side of the planned Hello Economy. While 60% of platform revenue is intended for $HELLO market buybacks and burn, the remaining **40% is planned for market buybacks of selected tokens launched through Hello.Fun**. The idea is to connect Hello.Fun platform activity not only with $HELLO, but also with the wider ecosystem of projects launching through the platform. ### The Planned Allocation The Hello Economy proposes the following platform revenue allocation: | Allocation | Share | | ------------------------ | ----: | | $HELLO Market Buybacks | 60% | | Selected Launch Buybacks | 40% | ```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"] ``` Launch Buybacks refer specifically to the 40% side of this planned model. ### What Is a Launch Buyback? A Launch Buyback uses part of the planned ecosystem allocation to purchase a selected Hello.Fun token through its market. ```mermaid flowchart LR A["Launch Buyback Allocation"] --> B["Selected Hello.Fun Token"] B --> C["Market Buyback"] ``` The model is designed around market purchases rather than taking tokens from creators or holders. ### Selected Launches Launch Buybacks are not intended to apply automatically to every token created through Hello.Fun. Projects would be selected according to the Hello Economy's planned selection framework. ```mermaid flowchart TD A["Hello.Fun Launches"] --> B["Project Selection"] B --> C["Selected Launches"] C --> D["Eligible for Launch Buybacks"] ``` This allows the Launch Buyback allocation to focus on selected projects within the ecosystem. ### Connecting Platform Growth With Launches The purpose of Launch Buybacks is to create an economic connection between Hello.Fun activity and projects growing through the platform. ```mermaid flowchart LR A["Platform Activity"] --> B["Platform Revenue"] B --> C["40% Launch Allocation"] C --> D["Selected Launches"] D --> E["Market Buybacks"] ``` Instead of platform revenue flowing only toward the platform token, the planned model reserves part of the economic loop for selected Hello.Fun launches. ### Market Buybacks Launch Buybacks are intended to take place through the selected token's market. This creates market activity around the selected launch as part of the Hello Economy. The model does not describe the 40% allocation as a direct payment to project teams. It is designed as a **market buyback allocation**. ### Buybacks and Creator Earnings Are Different Launch Buybacks are separate from creator fees. Creator fees are generated directly through trading activity around an individual launch. Launch Buybacks are part of the planned Hello Economy and would use the platform revenue allocation. | Mechanism | Source | | --------------- | -------------------------------------------- | | Creator Fees | Trading activity around the creator's launch | | Launch Buybacks | Planned 40% allocation of platform revenue | The two mechanisms serve different purposes. ### Buybacks and Liquidity Are Different Launch Buybacks are also separate from the liquidity created when a token graduates. Graduated liquidity comes from the launch lifecycle and remains permanently locked. Launch Buybacks are planned market purchases that would occur as part of the Hello Economy. ```mermaid flowchart TD A["Hello.Fun Token"] --> B["Graduation Liquidity"] A --> C["Potential Launch Buybacks"] B --> D["Permanent Liquidity"] C --> E["Market Purchases"] ``` One supports the market's liquidity structure. The other represents planned ecosystem market activity. ### Selection Framework The planned Launch Buyback model considers factors including: 1. Volume 2. Holders 3. Bubblemaps 4. Tokenomics 5. Team 6. Market Cap These factors are intended to help determine which Hello.Fun launches may be selected for ecosystem buybacks. The selection model is covered in greater detail in Project Selection. ### The Broader Loop Launch Buybacks extend the Hello Economy beyond $HELLO. ```mermaid flowchart TD A["Hello.Fun Activity"] --> B["Platform Revenue"] B --> C["Hello Economy"] C --> D["$HELLO Buybacks"] C --> E["Launch Buybacks"] D --> F["$HELLO Ecosystem"] E --> G["Selected Hello.Fun Markets"] ``` The planned model therefore creates two economic paths from platform revenue. One supports the $HELLO side of the ecosystem. The other creates market buyback activity around selected launches. ### Current Status Launch Buybacks are part of the planned Hello Economy. They are not currently active within the deployed Hello.Fun protocol. The current system does not automatically allocate 40% of platform revenue to launch buybacks, and automated project selection is not currently active. Until the Hello Economy is introduced, normal trading activity, creator fees and the deployed market structure operate independently of this planned allocation. ### Growing the Ecosystem Together The Launch Buyback model is designed around a broader idea: Hello.Fun should not only provide the infrastructure for projects to launch. Its planned economy is designed to create a connection between the growth of the platform and selected projects growing through it. **Platform Activity → Platform Revenue → Selected Launches → Market Buybacks** $HELLO is one side of the Hello Economy. The projects launching through Hello.Fun are the other. --- # 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/launch-buybacks.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.