> 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/project-selection.md). # Project Selection The planned Hello Economy allocates 40% of platform revenue to market buybacks of selected Hello.Fun launches. Not every token launched through Hello.Fun is intended to automatically receive Launch Buybacks. Project Selection is the planned process for determining which launches may be selected for this part of the ecosystem. ### Why Selection Exists Hello.Fun can support many launches. The Launch Buyback allocation is designed to focus on selected projects rather than being distributed automatically across every token. ```mermaid flowchart TD A["Hello.Fun Launches"] --> B["Project Selection"] B --> C["Selected Projects"] C --> D["Launch Buyback Allocation"] ``` Selection is intended to consider multiple market and project characteristics of a launch. ### Selection Factors The planned framework considers factors including: 1. Volume 2. Holders 3. Bubblemaps 4. Tokenomics 5. Team 6. Market Cap These factors are intended to be considered together rather than treating one metric as the entire basis for selection. ### Volume Volume provides information about market activity around a launch. Hello.Fun already indexes trading activity across its markets. Within the planned selection framework, volume can be considered as one signal when evaluating a project. High volume alone does not define selection. ### Holders Holder information can provide another view of participation around a token. The number of holders provides context around participation in a token. Within the planned selection framework, holder information can be considered alongside the other selection factors. ### Bubblemaps Bubblemaps is included as one of the planned Project Selection factors. Within the planned framework, it can provide additional context when reviewing a project alongside its volume, holders, tokenomics, team and market cap. Bubblemaps is a planned evaluation input. It is not currently integrated into Hello.Fun as an automated Project Selection system. ### Tokenomics The project's tokenomics can also form part of the selection process. This can include how the token economy is structured and how that structure relates to the project's broader market. Tokenomics is one part of the overall review rather than a standalone guarantee of selection. ### Team The planned framework also considers the team behind a project. This adds project level context alongside purely market based information. The Hello Economy is designed to evaluate selected launches using multiple signals rather than relying only on short term trading activity. ### Market Cap Market Cap provides context around the current size of a token's market. ```mermaid flowchart LR A["Token Price"] --> C["Market Cap"] B["Token Supply"] --> C C --> D["Selection Context"] ``` Like the other factors, Market Cap is intended to be considered as part of the broader project picture. ### Looking at the Whole Project The planned selection approach can be represented as multiple signals coming together. ```mermaid flowchart TD A["Volume"] --> G["Project Review"] B["Holders"] --> G C["Bubblemaps"] --> G D["Tokenomics"] --> G E["Team"] --> G F["Market Cap"] --> G G --> H["Selection Decision"] ``` No single factor is intended to automatically determine the result. ### No Fixed Public Score The planned Hello Economy does not currently define a fixed public scoring formula, weighting system or automatic qualification threshold for Project Selection. The selection factors describe what may be considered. They should not be interpreted as a guaranteed formula where reaching a particular number automatically qualifies a token for Launch Buybacks. ### Selection Does Not Guarantee Buybacks Launching through Hello.Fun does not automatically make a project eligible for Launch Buybacks. Likewise, performing strongly on one individual metric does not guarantee selection. Launch Buybacks are intended for projects selected through the broader Hello Economy process. ### Market Data and Additional Review Some selection factors can be informed by market data already tracked through Hello.Fun, including volume, holders and market cap. The remaining factors form part of the broader planned project review. ```mermaid flowchart TD A["Indexed Market Data"] --> C["Project Review"] B["Additional Selection Factors"] --> C C --> D["Selection"] ``` This allows the planned framework to consider multiple categories of information rather than relying on a single metric. ### Current Status Project Selection is part of the planned Hello Economy. There is currently no automated Project Selection system operating within the deployed Hello.Fun protocol. There is also no active scoring formula automatically selecting projects for the planned 40% Launch Buyback allocation. The criteria on this page describe the intended framework for the Hello Economy. ### Selection Within the Hello Economy Project Selection connects the broader Hello.Fun launch ecosystem with the planned Launch Buyback model. ```mermaid flowchart LR A["Hello.Fun Launches"] --> B["Project Selection"] B --> C["Selected Launches"] C --> D["Launch Buybacks"] D --> E["Hello Economy"] ``` The goal is not simply to identify the token with the largest single metric. It is to consider the wider picture around a launch before directing planned ecosystem buyback activity toward 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/project-selection.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.