> 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/meme-token-pairs.md). # Meme Token Pairs Meme tokens are planned as a future pairing category on Hello.Fun. The idea is to allow creators to launch new tokens against supported meme tokens, giving established meme assets a new role as the starting market for new launches. ### Launching Against a Meme Token When meme token pairing becomes available, creators will be able to choose from supported meme tokens during the launch process. ```mermaid flowchart LR A["Create Token"] --> B["Choose Pair"] B --> C["Supported Meme Token"] C --> D["Launch"] D --> E["New Pair Market"] ``` The selected meme token becomes the pairing asset for the new launch. ### Through the Launch Lifecycle A meme token pair is designed to remain connected to the launch throughout its market lifecycle. ```mermaid flowchart LR A["New Token + Meme Token"] --> B["Bonding Curve"] B --> C["Pair Reserves"] C --> D["Graduation"] D --> E["Uniswap v4 Pair Market"] ``` The pair begins with the bonding curve and continues into the graduated market. ### Giving Existing Tokens New Utility Meme token pairing is designed to create utility for tokens that already have their own communities and markets. Instead of only being traded as standalone assets, supported meme tokens can become the pairing assets behind new Hello.Fun launches. ```mermaid flowchart TD A["Supported Meme Token"] --> B["Pairing Asset"] B --> C["New Launch"] C --> D["New Market"] ``` Every new launch can create another market involving the meme token it pairs with. ### One Meme Token, Multiple Markets A supported meme token could potentially become the pairing asset for multiple Hello.Fun launches. ```mermaid flowchart TD A["Supported Meme Token"] --> B["Launch A"] A --> C["Launch B"] A --> D["Launch C"] B --> E["New Pair Market"] C --> F["New Pair Market"] D --> G["New Pair Market"] ``` This allows an existing asset to become part of the market structure of new tokens. ### Trading With the Pair For a meme paired launch, the selected meme token would be used as the market asset. Users would use the pairing asset when buying the launched token and receive the pairing asset when selling. ```mermaid flowchart LR A["Meme Pair Asset"] --> B["Market"] B --> C["Launched Token"] ``` The same pairing relationship would continue after graduation. ### Pair Specific Economics Meme token pairs can have their own configured market economics. Hello.Fun's pairing system is designed to support pair specific settings including: 1. Phantom liquidity 2. Graduation conditions ```mermaid flowchart TD A["Supported Meme Token"] --> B["Pair Economics"] B --> C["Phantom Liquidity"] B --> D["Graduation Conditions"] C --> E["Launch Market"] D --> E ``` This allows supported meme pairs to be configured for their market characteristics. ### Supported Meme Tokens Meme token pairing will use a curated set of supported assets. Creators will choose from the meme tokens made available by Hello.Fun rather than entering an arbitrary token address. ```mermaid flowchart LR A["Meme Token"] --> B["Approved and Configured"] B --> C["Supported Pair"] C --> D["Available for New Launches"] ``` The supported list can expand as the Hello.Fun pairing ecosystem grows. ### Pairing Markets and Communities Meme tokens often develop communities around the asset itself. Pairing creates a way for a new launch to begin within a market connected to an existing meme token. ```mermaid flowchart LR A["Existing Meme Token"] --> B["Existing Ecosystem"] A --> C["New Hello.Fun Pair"] C --> D["New Token Market"] ``` This gives creators another dimension to consider when deciding how their token enters the market. ### More Than a Trading Pair The Hello.Fun pairing model is designed to make existing assets useful within new launches. For meme tokens, this means a supported asset can become part of the infrastructure behind another token's market. **Existing token → New pair → New market** The pair becomes part of the launch idea. ### Current Status Meme token pairing is planned and is not currently available within the deployed Hello.Fun launch system. ETH is currently the live pairing asset. The meme tokens available for pairing will depend on the supported assets approved and configured when this category is introduced. ### Where Memes Meet New Markets Meme token pairing extends Hello.Fun beyond the idea that every new token should launch against the same asset. Creators gain more choice. Existing tokens gain another potential use. New pair markets become possible. **Pick your pair. Launch your token. Say HELLO to what’s next.** --- # 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/meme-token-pairs.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.