> 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/what-is-hood.fun.md). # What is Hood.Fun ? ## What is hood.fun A normal launchpad token is pure momentum. Its supply stays fixed, and once it graduates the story rarely changes. hood.fun adds a second engine. Every token carries a **perpetual futures bet** chosen by its creator. During bonding, 10% of each buy is reserved for that bet. After graduation, the capital is deployed on Lighter — and each time the bet reaches its profit target, that profit buys the token and burns what it receives. ### What that gives you * **A bet with consequences.** Long or short, 1× to 5×: the creator's call becomes part of the token's mechanics, not just its branding. * **Irreversible scarcity.** A winning round removes tokens from supply forever. The perp itself does not set the price; it creates real buy pressure and burns. * **A simple market.** The token starts on a bonding curve, then moves to one permanently locked public pool. No liquidity unlock hangs over holders. ### What a creator chooses At launch, the creator sets three things: * the **underlying** — e.g. NVDA, BTC, GOLD, an index… * the **direction** — long or short * the **leverage** — from 1× to 5× Everything after that is automatic: bonding, graduation, perp execution, profit-taking and burns are handled by the protocol and its keeper. {% hint style="info" %} New here? Read [The token lifecycle](/traders/the-token-lifecycle.md) next — it's the map for everything else. {% endhint %} --- # 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/what-is-hood.fun.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.