> 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/token-metadata.md). # Token Metadata Token metadata gives a Hello.Fun launch its public identity. It connects the token contract with the information displayed across the Hello.Fun interface, including the token image, description and project links. Because the metadata reference becomes permanent at launch, creators should make sure everything is correct before confirming the transaction. ### What Token Metadata Includes When creating a token, the creator can provide: * Token name * Token symbol * Description * Token image * Website * X profile * Telegram community This information is used to present the token across Hello.Fun. ### Using HELLO Pilot Creators can prepare their token information manually or use HELLO Pilot for AI assistance during the creation process. Pilot can assist creators as they build the identity and information around their launch. The creator should still review all generated or prepared information carefully before launching, since the metadata reference becomes permanent once the token is created. ### How Metadata Is Added Token metadata is prepared before the token is launched. The metadata is stored through the Hello.Fun metadata service, and its reference is included when the token is created onchain. ```mermaid flowchart LR A["Creator Adds Token Information"] --> B["Metadata Prepared"] B --> C["Metadata Reference Created"] C --> D["Token Launch"] D --> E["Reference Written Into Token"] E --> F["Token Information Displayed"] ``` This connects the launched token with its public project information. ### Metadata Is Set at Launch The metadata reference is established when the token is created. Once the token has launched, that reference cannot be changed. This means creators should treat the metadata review as an important part of the launch process. ### Review Before You Launch Before confirming the launch, check: * Token name * Token symbol * Description * Token image * Website * X profile * Telegram community Check spelling, links and images carefully. Whether the information was prepared manually or with assistance from HELLO Pilot, the creator should review the final metadata before confirming the launch. Once the launch is confirmed, the metadata reference associated with the token is permanent. ### Token Identity and Token Logic Metadata describes the token, but it does not control how the token itself behaves. The token contract separately defines the fixed supply and ERC20 behavior. ```mermaid flowchart TD A["Hello.Fun Token"] --> B["Token Contract"] A --> C["Token Metadata"] B --> D["Fixed Supply"] B --> E["ERC20 Transfers"] B --> F["Token Structure"] C --> G["Description"] C --> H["Image"] C --> I["Project Links"] ``` Changing information outside Hello.Fun does not change the token contract or its onchain metadata reference. ### Metadata and Market Data Token metadata and market data serve different purposes. Metadata describes the token and project. Market data reflects activity around the token. Market data can change continuously as users trade, while the token's metadata reference remains fixed. Market information is derived from indexed blockchain activity rather than being manually entered by the creator. ### Built for a Permanent Launch A token launch is different from creating a normal editable profile. The token becomes an onchain asset, and its metadata reference becomes part of that launch. Creators should therefore prepare their token identity carefully before submitting the final transaction. **Review first. Launch once.** --- # 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/token-metadata.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.