> 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/after-you-launch.md). # After You Launch Once your launch transaction is confirmed, your token enters its first live market. The token has been created, its fixed supply has been placed into the bonding curve and trading can begin. From this point, the launch starts progressing through the Hello.Fun market lifecycle. ### Your Market Is Live Trading opens as part of the launch process. There is no separate activation step required from the creator. ```mermaid flowchart LR A["Launch Confirmed"] --> B["Token Created"] B --> C["Supply Enters Bonding Curve"] C --> D["Market Opens"] D --> E["Trading Begins"] ``` Users can now buy and sell the token through its bonding curve. ### Your Token Supply Is Fixed Every Hello.Fun token launches with a total supply of **1,000,000,000 tokens**. The supply is created once at launch. After launch, the creator cannot mint additional tokens through the token contract. The creator also cannot use the token contract to blacklist wallets or freeze standard token transfers. ### Trading Begins on the Bonding Curve The bonding curve is the token's first market. Buyers provide the pairing asset and receive tokens. Sellers can return tokens and receive the pairing asset. As trading takes place, the market progresses along the bonding curve and builds the reserves used for graduation. ### Your Creator Fee Begins Accruing If a creator fee was selected for the launch, it can begin accruing from eligible trading activity. Creator fees are not automatically sent to the creator after every trade. They accumulate through the Hello.Fun fee system and can be claimed by the creator. The creator fee selected at launch remains fixed. ### Market Data Begins Building Hello.Fun indexes blockchain activity and turns it into readable market information. As users interact with the token, its page can reflect data such as: * Price * Market capitalization * Trading volume * Holder information * Transactions * Charts * Pair information The market data develops from actual blockchain activity around the token. ### Intelligence Around Your Market A live token creates more than a trading market. It also creates activity, data and a growing project history. HELLO Intelligence is designed to help creators and traders make more sense of that information through focused AI powered products across token analysis, project understanding, activity monitoring, discovery and growth. As these products are introduced across Hello.Fun, they will build on the market and project information surrounding a token without changing the underlying market mechanics. The HELLO Intelligence section explains these products and their availability in more detail. ### Progress Toward Graduation The bonding curve is the first stage of the market, not the final one. As the launch progresses, it moves toward its graduation conditions. ```mermaid flowchart LR A["Launch"] --> B["Bonding Curve Trading"] B --> C["Reserves Build"] C --> D["Graduation Conditions Reached"] D --> E["Graduation"] ``` Once those conditions are reached, the token becomes ready to move from the bonding curve into its Uniswap v4 market. ### Graduation Can Complete Without the Creator The creator does not need to personally execute the final market transition. When the launch reaches graduation, the protocol can attempt to complete the process automatically. If automatic completion does not succeed, graduation can still be completed through the protocol by another user. This keeps the market transition from depending on the creator returning to perform a specific action. ### What Happens at Graduation Graduation moves the launch into its next market stage. The accumulated reserves are moved through the graduation process and used to establish the token's Uniswap v4 liquidity pool. The resulting liquidity position is then transferred into the Hello.Fun liquidity locker. ```mermaid flowchart TD A["Graduation"] --> B["Reserves Moved"] B --> C["Uniswap v4 Pool Created"] C --> D["Liquidity Position Created"] D --> E["Liquidity Transferred to Locker"] E --> F["Trading Continues"] ``` ### Liquidity Becomes Permanent Once the graduated liquidity position enters the Hello.Fun liquidity locker, the liquidity principal cannot be withdrawn, unlocked, transferred or removed from the locker. The creator does not receive control of the graduated liquidity position. The liquidity remains part of the token's continuing market. ### Trading Continues Graduation does not close the market. It changes where trading takes place. Before graduation, users trade through the bonding curve. After graduation, users trade through the Uniswap v4 market. ```mermaid flowchart LR A["Bonding Curve Trading"] --> B["Graduation"] B --> C["Uniswap v4 Trading"] ``` ### The Creator Journey Launching through Hello.Fun is the beginning of the market lifecycle rather than the end of it. **Launch → Trade → Build Reserves → Graduate → Lock Liquidity → Continue Trading** The creator establishes the token and its launch settings. From there, market activity drives the token toward its next stage, while the wider Hello.Fun ecosystem is designed to provide additional intelligence around the token and its market. --- # 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/after-you-launch.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.