> 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/graduation.md).

# Graduation

Graduation happens automatically the moment a token's bonding curve accumulates enough real LT reserve — a threshold set per-launch when the token is created. There's no single platform-wide number; each launch configures its own.

Because the threshold is measured in the LT the curve holds (not a fixed USD figure), graduation can be reached through token buys, through the LT's NAV appreciating, or a mix of both — and it can move further away if the underlying asset moves against the LT's direction.

Graduating a token is a single on-chain call, triggerable by anyone once the threshold is met — no separate keeper step is required. It:

1. Creates (or reuses) a Uniswap V2 pool for the token, paired with its backing LT.
2. Seeds that pool with the curve's LT and remaining token supply.
3. Locks the resulting LP position on-chain, with an unlock time chosen at launch.
4. Clears out any leftover dust — unsold tokens are burned, leftover LT goes to the LP beneficiary.

After graduation, the token trades as a standard ERC-20 on the open Uniswap V2 pool. The LT stays the paired asset, so the leverage effect on price keeps working exactly as it did on the curve.


---

# 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/graduation.md?ask=<question>&goal=<endgoal>
```

`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.