> 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-sell.md). # How to Sell ## How to Sell Hello.Fun lets users sell tokens directly through the token's market. The route depends on whether the token is still trading on its bonding curve or has graduated to Uniswap v4. ### Before You Sell To sell a token, you need: * The token in your connected wallet * Your wallet connected to Hello.Fun * Robinhood Chain selected * Enough ETH to cover network gas For current ETH paired launches, selling exchanges the launched token for ETH. ### Open the Token Page Find the token and open its token page. Select the sell option and enter the amount of tokens you want to trade. ```mermaid flowchart LR A["Token Page"] --> B["Select Sell"] B --> C["Enter Amount"] C --> D["Review Quote"] D --> E["Sign Transaction"] ``` ### The Trading Route Hello.Fun uses the appropriate market based on the token's current stage. ```mermaid flowchart TD A["Sell Token"] --> B{"Market Stage"} B -->|"Bonding Curve"| C["Bonding Curve Sell"] B -->|"Graduated"| D["Uniswap v4 Swap"] ``` Selling through the bonding curve remains available until the launch is ready to graduate. After graduation, selling takes place through the Uniswap v4 pool. ### Selling on the Bonding Curve During the bonding curve stage, users can sell tokens back through the curve until the launch is ready to graduate. For an ETH paired launch: ```mermaid flowchart LR A["Launched Token"] --> B["Bonding Curve"] B --> C["ETH"] C --> D["Seller Wallet"] ``` The amount received depends on the current bonding curve state, trade size, fees and slippage protection. ### Selling After Graduation Once graduation is complete, normal trading moves to the token's Uniswap v4 pool. ```mermaid flowchart LR A["Launched Token"] --> B["Uniswap v4 Pool"] B --> C["ETH"] C --> D["Seller Wallet"] ``` The sell quote is then obtained from the graduated market rather than the bonding curve. ### Review the Quote Before submitting a sell, review the available trade information. This can include: * Expected output * Minimum output * Slippage tolerance * Price impact * Applicable trading fees * Network gas Market conditions can change between the time a quote is displayed and the time a transaction executes. ### Slippage Protection Sell transactions use minimum output protection. Your slippage setting determines the minimum amount of the pairing asset you are willing to receive. ```mermaid flowchart TD A["Sell Quote"] --> B["Slippage Setting"] B --> C["Minimum Output"] C --> D["Transaction Submitted"] D --> E{"Minimum Output Met?"} E -->|Yes| F["Sell Completes"] E -->|No| G["Transaction Reverts"] ``` If the minimum output cannot be satisfied, the transaction reverts rather than completing outside the accepted tolerance. ### Price Impact Selling can affect the market price. The effect depends on the size of the trade relative to the current market. Hello.Fun displays price impact so users can review the expected effect before confirming the transaction. ### Trading Fees During the bonding curve stage, a sell includes: * **1% Protocol Fee** * **Creator Fee** After graduation, a sell includes: * **1% Protocol Fee** * **Creator Fee** There is **no separate 1% liquidity fee** after graduation. Network gas is separate. ### Token Approval Selling a token can require permission for the trading system to use the token amount involved in the transaction. Where an approval is required, the wallet must authorize it before the corresponding token amount can be used for the trade. This is separate from the sell transaction itself. ### Sign With Your Wallet The user authorizes state changing actions through their connected wallet. Hello.Fun does not hold user private keys or sign sell transactions on behalf of users. ```mermaid flowchart LR A["Review Sell"] --> B["Wallet Authorization"] B --> C["Onchain Transaction"] C --> D["Trade Executes"] D --> E["Pairing Asset Received"] ``` ### After the Sale Once the transaction successfully completes, the resulting pairing asset is received by the user's wallet. The trade is also part of the onchain activity indexed by Hello.Fun. ```mermaid flowchart LR A["Sell Completes"] --> B["Pairing Asset to Wallet"] A --> C["Onchain Trade Event"] C --> D["Hello.Fun Indexer"] D --> E["Market Data Updated"] ``` ### Selling Across the Token Lifecycle Hello.Fun keeps the sell experience connected as the token moves between market stages. **Before Graduation:** Token → Bonding Curve → ETH **After Graduation:** Token → Uniswap v4 → ETH The execution market changes. The user still controls the transaction through their wallet. --- # 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-sell.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.