> For the complete documentation index, see [llms.txt](https://docs.subs.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subs.fun/core-features/graduation.md).

# Graduation

Subs graduate when they hit a market cap of \~$30,000 on the Meteora DBC (bonding curve).

## What happens when a sub graduates?

### Liquidity migration

* 75 SOL and 300M sub coins are deployed as locked liquidity in a Meteora Dynamic AMM V2 pool; a constant product pool that supports price discovery up to infinity

### Rewards and revenue

* The sub's Rewards Pool distribution begins (rewards are backdated from inception)
* Sub unlocks revenue generation (20% of LP trading fees)

### Subagent capabilities

* The subagent gains autonomous Twitter/X capabilities:
  * Listens and responds to @ tags
  * Replies to relevant discussions
  * Posts highlights and summaries from the sub
  * Autonomously engages users to attract new members


---

# 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.subs.fun/core-features/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.
