> 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/whats-next/expanding-pair-choice.md). # Expanding Pair Choice Hello.Fun begins with ETH as its live pairing asset. The broader vision goes further. Hello.Fun is designed so that creators can eventually choose from multiple supported pairing assets when launching a token, making the pair itself part of the launch strategy. **Pick your pair. Pick your market.** ### Beyond a Single Pair Most token launches begin against the same standard market. Hello.Fun is designed around a different idea. The creator chooses not only what token to launch, but also what supported asset that token launches against. ```mermaid flowchart TD A["Create Token"] --> B["Choose Pair"] B --> C["ETH"] B --> D["$HELLO"] B --> E["Tokenized Stocks"] B --> F["Meme Tokens"] ``` ETH is currently live. $HELLO, tokenized stocks and meme token pairs form part of the planned expansion of pair choice. ### Why Pair Choice Matters A pair defines the market around a token. It determines: 1. What users use to buy the token 2. What users receive when selling 3. What asset builds reserves during the bonding curve 4. What pair graduates into the Uniswap v4 market 5. What existing ecosystem the new token can connect with Choosing a pair is therefore more than a technical setting. It helps define the market the token enters. ### One Launch, Different Market Possibilities As pair choice expands, two creators could launch different tokens through Hello.Fun while choosing entirely different starting markets. ```mermaid flowchart TD A["Hello.Fun Launch"] --> B["Choose Supported Pair"] B --> C["ETH Market"] B --> D["$HELLO Market"] B --> E["Tokenized Stock Market"] B --> F["Meme Token Market"] ``` The launch mechanism can remain consistent while the pairing asset changes. ### Pairing From Launch to Graduation A selected pairing asset is designed to remain part of the token throughout its market lifecycle. ```mermaid flowchart LR A["Choose Pair"] --> B["Bonding Curve"] B --> C["Build Reserves"] C --> D["Graduation"] D --> E["Uniswap v4 Market"] ``` The pair used during the bonding curve becomes the pair used when the graduated market is established. This creates continuity from launch to open market. ### Curated Pair Support Expanding pair choice does not mean allowing any arbitrary token address to become a Hello.Fun pairing asset. Pair assets are approved and configured by Hello.Fun before they can be used for new launches. ```mermaid flowchart LR A["Potential Pair Asset"] --> B["Hello.Fun Support"] B --> C["Approved Pair"] C --> D["Available for New Launches"] ``` This allows each supported pair to have the market configuration required for the Hello.Fun launch lifecycle. ### Pair Specific Economics Different pairing assets can require different market economics. Hello.Fun's pairing system supports pair specific configuration for areas including: 1. Phantom liquidity 2. Graduation conditions This allows the launch model to support different pairing assets without requiring every market to use identical economic settings. ### $HELLO Pairs $HELLO is planned as a future pairing option within Hello.Fun. A $HELLO paired launch would create a market directly between the new token and $HELLO. ```mermaid flowchart LR A["New Token"] --> B["$HELLO Pair"] B --> C["Bonding Curve"] C --> D["Graduation"] D --> E["Token + $HELLO Market"] ``` $HELLO pairing is also designed to connect with the broader creator incentive and Hello Economy model. ### Tokenized Stock Pairs Hello.Fun also plans to introduce supported tokenized stocks as pairing assets. This would allow a new token to begin its market against a supported tokenized stock rather than only ETH. ```mermaid flowchart LR A["New Token"] --> B["Supported Tokenized Stock"] B --> C["Pair Market"] ``` The specific supported stock pairs will depend on the assets approved for the platform as this part of the ecosystem is introduced. ### Meme Token Pairs Supported meme tokens are another planned pairing category. A creator could choose a supported meme token as the market for a new launch. ```mermaid flowchart LR A["Existing Meme Token"] --> B["Pair Asset"] B --> C["New Hello.Fun Launch"] C --> D["New Pair Market"] ``` This creates a new role for existing meme tokens inside future Hello.Fun markets. ### New Markets for Existing Tokens Pair expansion is not only about giving creators more choices. It can also create new utility for the assets used as pairs. Every new launch can create another market involving its selected pairing asset. ```mermaid flowchart TD A["Supported Pair Asset"] --> B["Launch A"] A --> C["Launch B"] A --> D["Launch C"] B --> E["New Market"] C --> F["New Market"] D --> G["New Market"] ``` A pairing asset can therefore become part of multiple new token markets across Hello.Fun. ### Current and Planned Pairing | Pair Category | Status | | ---------------- | ------- | | ETH | Live | | $HELLO | Planned | | Tokenized Stocks | Planned | | Meme Tokens | Planned | Hello.Fun is starting with one live pair while building toward a broader pair focused ecosystem. ### Where Stocks Meet Memes The long term pairing model brings together markets that would normally exist separately. ETH. $HELLO. Tokenized stocks. Meme tokens. All as potential building blocks for new token markets. **Not your regular launchpad. Where stocks meet memes.** Hello.Fun is designed for a future where choosing the token is only half the launch. **The pair is part of the idea.** --- # 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/whats-next/expanding-pair-choice.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.