> 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/explore-and-trading/how-to-buy.md). # How to Buy Hello.Fun lets users buy tokens directly from their token page. The trading route depends on the token's current market stage. Before graduation, the purchase takes place through the bonding curve. After graduation, the purchase takes place through the token's Uniswap v4 market. ### Before You Buy To buy a token, you need: * A compatible EVM wallet * Your wallet connected to Hello.Fun * Robinhood Chain selected in your wallet * Enough of the pairing asset for the purchase * Enough ETH to cover network gas ETH is currently the live pairing asset on Hello.Fun. ### Open the Token Page Find the token through Explore, Trending, New or Search. Open its token page to review the project and market before preparing your trade. ```mermaid flowchart LR A["Explore"] --> B["Find Token"] B --> C["Open Token Page"] C --> D["Review Market"] D --> E["Prepare Buy"] ``` ### Enter Your Buy Choose the buy option and enter the amount you want to trade. Hello.Fun determines whether the token is still on its bonding curve or has already graduated. ```mermaid flowchart TD A["Buy Token"] --> B{"Market Stage"} B -->|"Before Graduation"| C["Bonding Curve"] B -->|"After Graduation"| D["Uniswap v4"] ``` The correct market is used automatically. ### Buying Before Graduation Before graduation, the purchase is executed against the token's bonding curve. For an ETH paired token: ```mermaid flowchart LR A["ETH"] --> B["Bonding Curve"] B --> C["Launched Token"] C --> D["Buyer Wallet"] ``` The bonding curve determines the expected token output according to its current state. As buying activity changes the curve, the token price can also change. ### Buying After Graduation Once the token graduates, buying moves to the Uniswap v4 pool created during graduation. ```mermaid flowchart LR A["ETH"] --> B["Uniswap v4 Pool"] B --> C["Launched Token"] C --> D["Buyer Wallet"] ``` Hello.Fun obtains the quote from the graduated market rather than the bonding curve. ### Review the Quote Before signing, review the trade information shown by Hello.Fun. This can include: * Expected token output * Slippage tolerance * Minimum output * Price impact * Applicable trading fees * Network gas The quote reflects the current state of the market. ### Slippage Protection Hello.Fun uses minimum output protection for trades. Your slippage setting determines the minimum amount of tokens you are willing to receive. ```mermaid flowchart TD A["Trade Quote"] --> B["Slippage Setting"] B --> C["Minimum Output"] C --> D["Transaction Submitted"] D --> E{"Minimum Output Met?"} E -->|Yes| F["Buy Completes"] E -->|No| G["Transaction Reverts"] ``` If the trade cannot meet the minimum output specified in the transaction, it does not complete. ### Price Impact Price impact shows how much the trade itself may affect the market price. Larger trades relative to the available market can produce greater price impact. Review the displayed price impact before signing your transaction. ### Trading Fees Before graduation, a buy includes: * **1% Protocol Fee** * **Creator Fee** After graduation, a buy includes: * **1% Protocol Fee** * **Creator Fee** There is **no separate 1% liquidity fee** after graduation. Network gas is separate. ### ETH Buys Do Not Require Token Approval When buying an ETH paired launch with ETH, there is no ERC20 token approval required for the ETH being spent. The user prepares the trade and signs the transaction through their wallet. ### Sign With Your Wallet Hello.Fun does not execute a purchase without your wallet authorization. Once you are satisfied with the quote and trade settings, confirm the transaction in your connected wallet. ```mermaid flowchart LR A["Prepare Buy"] --> B["Review Quote"] B --> C["Sign With Wallet"] C --> D["Transaction Executes Onchain"] D --> E["Tokens Received"] ``` Hello.Fun does not hold your private keys or sign the transaction for you. ### After the Purchase Once the transaction completes, the purchased tokens are delivered to your wallet. The resulting market activity is indexed by Hello.Fun and reflected in the platform's market data. ```mermaid flowchart LR A["Buy Completes"] --> B["Tokens to Wallet"] A --> C["Onchain Trade Event"] C --> D["Hello.Fun Indexer"] D --> E["Updated Market Data"] ``` ### Buying Across the Token Lifecycle The buying experience follows the token wherever it is in its market lifecycle. **Before Graduation:** ETH → Bonding Curve → Token **After Graduation:** ETH → Uniswap v4 → Token The market route changes after graduation. The user experience remains connected through Hello.Fun. --- # 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/explore-and-trading/how-to-buy.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.