> For the complete documentation index, see [llms.txt](https://docs.hoodfun.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hoodfun.xyz/creating-a-token.md). # Creating a token Anyone can launch a token through the hood.fun meme launcher — it's permissionless. #### Token details * Name and ticker * The backing LT — must be a leveraged token already registered on-chain; Long / Short up to x5 * Metadata can't be changed after launch #### Supply Every token has a fixed supply, minted entirely to its bonding curve at launch — 1,000,000,000 tokens by default, though a launch can configure a different total. #### Launch fee Launching a token requires a small native-token fee, paid to the protocol's fee vault to deter spam. The fee amount is set at deploy time, not fixed by the protocol. #### Backing LT The only requirement on the backing asset is that it's a real, registered LT — the launcher checks this on-chain before allowing a launch. You can't back a token with an arbitrary token, or an LT that hasn't been through the registration process. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hoodfun.xyz/creating-a-token.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.