> 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/launching-a-token/launch-settings.md). # Launch Settings Launch settings define how a token enters the Hello.Fun market. Before launching, the creator reviews the pairing asset and chooses the creator fee that will apply to the launch. Once the launch is confirmed onchain, these settings become part of that launch and cannot be freely changed afterward. ### Pairing Asset Every Hello.Fun launch has a pairing asset. The pairing asset determines what asset the new token trades against during its bonding curve stage and later in its graduated Uniswap v4 market. ETH is currently the live pairing asset available for new launches. As Hello.Fun expands, additional approved pairing assets can be introduced through the pairing system. ### Creator Fee The creator can select a creator fee within the range supported by Hello.Fun. This fee applies to trading activity associated with that specific launch. Creator fees can accrue during: * Bonding curve trading * Uniswap v4 trading after graduation The creator fee selected at launch is fixed for that launch. It cannot be increased after the token has been created. ```mermaid flowchart LR A["Creator Selects Fee"] --> B["Launch Confirmed"] B --> C["Fee Becomes Fixed"] C --> D["Bonding Curve Trades"] C --> E["Uniswap v4 Trades"] D --> F["Creator Fees Accrue"] E --> F ``` ### Protocol Fee Hello.Fun also applies a protocol fee to trading. The protocol fee is separate from the creator fee. During the bonding curve stage, the protocol fee is **1% per trade**. After graduation, Hello.Fun also applies a **1% protocol fee** to swaps through the graduated market. The protocol fee rate cannot be increased for an existing launch. ### Understanding the Fees The fees that apply to trading depend on the stage of the market. #### Before Graduation Trading through the bonding curve can include: * **1% Protocol Fee** * **Creator Fee** #### After Graduation Trading through the graduated Uniswap v4 market can include: * **1% Protocol Fee** * **Creator Fee** The creator fee is subject to the limits supported by Hello.Fun and is established when the token launches. Network gas is separate from these trading fees. ### Deployment Fee Hello.Fun does not charge a platform Deployment Fee for creating a token. This applies to the launch itself. Creators still need ETH to cover the blockchain gas required to submit and execute the launch transaction on Robinhood Chain. ```mermaid flowchart TD A["Create Token"] --> B["Hello.Fun Deployment Fee"] B --> C["0"] A --> D["Blockchain Gas"] D --> E["Paid Through Wallet"] ``` ### Network Gas Network gas is not a Hello.Fun platform fee. It is the blockchain transaction cost required to execute an action on Robinhood Chain. Gas may be required when performing onchain actions such as: * Creating a token * Buying * Selling * Claiming accrued fees * Other blockchain transactions The exact gas cost depends on the network and the transaction being executed. ### What Becomes Fixed at Launch Some parts of a launch are established when the token is created. ```mermaid flowchart TD A["Launch Confirmed"] --> B["Token Supply Fixed"] A --> C["Creator Fee Fixed"] A --> D["Pairing Asset Fixed for Launch"] A --> E["Token Metadata Reference Fixed"] ``` The creator cannot later increase the token supply or raise the creator fee. Changes to the list of pairing assets available for future launches also do not alter the pairing asset or economics of an existing launch. ### Using HELLO Pilot Creators who prefer AI assistance can use HELLO Pilot instead of preparing every part of the launch manually. Pilot helps guide the creation process and prepare the launch configuration, while the creator remains in control of the final settings. Before the token is launched, the creator can review the configuration and approve the transaction through their own wallet. ### Review Before Launching Before confirming a launch, creators should review the complete configuration carefully. Check the token information, pairing asset, creator fee and metadata before signing the transaction. Once the launch transaction is executed, the core structure and settings of that launch are established onchain. ### Defined From the Start Hello.Fun is designed so that important launch properties are established when the market begins. The supply is fixed. The creator fee is fixed. The pairing asset is established. The token metadata reference is established. From there, the market progresses through trading and eventually toward graduation. --- # 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/launching-a-token/launch-settings.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.