> 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/understanding-a-token-page.md). # Understanding a Token Page Every Hello.Fun launch has its own token page. The token page brings together project information, live market data, trading activity and the tools needed to buy or sell the token. It follows the token from its bonding curve stage through graduation and into its Uniswap v4 market. ### Token Overview The token page identifies the launch and its market. Information can include: * Token name * Token symbol * Token image * Description * Pairing asset * Project website * X profile * Telegram The project information shown on the page comes from the metadata established when the token was created. ### Market Overview The token page also displays market information derived from indexed onchain activity. ```mermaid flowchart LR A["Onchain Activity"] --> B["Hello.Fun Indexer"] B --> C["Market Data"] C --> D["Token Page"] ``` This gives users a current view of the token's market alongside its project information. ### Understanding the Main Market Data A token page can include: * Price * Market capitalization * 24 hour volume * Holder information * Transactions * Charts * Pair information These figures are derived from the token's current market stage. ### Market Stage A Hello.Fun token can exist in one of two primary market stages. ```mermaid flowchart TD A["Hello.Fun Token"] --> B{"Market Stage"} B -->|"Before Graduation"| C["Bonding Curve"] B -->|"After Graduation"| D["Uniswap v4"] ``` Before graduation, pricing and trading are based on the bonding curve. After graduation, the token page follows the Uniswap v4 market. ### Price The source of the displayed token price depends on the market stage. Before graduation, price is derived from the bonding curve state. After graduation, price is derived from the Uniswap v4 market. ```mermaid flowchart TD A["Current Price"] --> B{"Graduated?"} B -->|No| C["Bonding Curve State"] B -->|Yes| D["Uniswap v4 Market"] ``` This allows the token page to continue displaying market information as the launch moves through its lifecycle. ### Market Cap Market cap is calculated using the token's supply and current market price. Hello.Fun launch tokens have a fixed total supply of **1,000,000,000 tokens**. ```mermaid flowchart LR A["Current Token Price"] --> C["Market Cap"] B["1,000,000,000 Token Supply"] --> C ``` The displayed USD value can use the relevant ETH to USD conversion for presentation. ### 24 Hour Volume Volume represents rolling trading activity over the previous 24 hours. Hello.Fun indexes both bonding curve trades and graduated pool swaps. If a token graduates during the relevant period, its volume can include activity from both market stages. ```mermaid flowchart TD A["24 Hour Volume"] --> B["Bonding Curve Trades"] A --> C["Uniswap v4 Swaps"] ``` This allows volume tracking to continue across graduation. ### Holders and Transactions Hello.Fun derives holder and transaction information from indexed blockchain events. Holder information provides visibility into token ownership activity. Transaction information provides visibility into market activity around the launch. These figures are generated from indexed onchain data rather than manually entered statistics. ### Charts Charts provide a visual view of the token's market activity over time. The underlying market changes when a token graduates, but the Hello.Fun data system continues tracking the launch across the transition. ```mermaid flowchart LR A["Bonding Curve Activity"] --> C["Indexed Market History"] B["Uniswap v4 Activity"] --> C C --> D["Token Chart"] ``` ### The Pair The token page identifies the asset paired with the launched token. For current Hello.Fun launches, the live pairing asset is ETH. The pair determines the market used for buying and selling and remains connected to the token through graduation. ### Trading Panel The token page provides access to buying and selling. Before graduation, trades are routed through the bonding curve. After graduation, trades are routed through the Uniswap v4 market. ```mermaid flowchart TD A["Trading Panel"] --> B{"Market Stage"} B -->|"Bonding Curve"| C["Curve Trade"] B -->|"Graduated"| D["Uniswap v4 Swap"] ``` Hello.Fun uses the appropriate trading route based on the token's current state. ### Trade Information Before signing a trade, users can review information such as: * Expected output * Slippage * Price impact * Applicable fees * Network gas The user then signs the transaction through their connected wallet. ### Beyond Market Data A token can have much more happening around it than price, volume and transactions alone can explain. HELLO Intelligence is designed to add deeper ways to understand tokens, projects and the activity surrounding them. Products such as HELLO Lens, HELLO Mate and The Scout will expand this experience through token analysis, AI powered project understanding and activity monitoring. Say Hello will take this further by bringing the wider world around a token together into a more complete intelligence and discovery experience. This can include market information, project information, social context, activity, intelligence and other signals around the token in one place. These products are covered individually in the HELLO Intelligence section, including their intended role and availability. ### From Information to Action A Hello.Fun token page connects project information with the live market. ```mermaid flowchart LR A["Project Information"] --> C["Token Page"] B["Onchain Market Data"] --> C C --> D["Review Market"] D --> E["Buy or Sell"] E --> F["Sign With Wallet"] ``` The token page is where discovery becomes market interaction. **Understand the token. Review the market. Choose your trade.** --- # 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/understanding-a-token-page.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.