> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/trading-before-and-after-graduation.md).

# Trading before and after graduation

A Pro token trades on its Curve first, then on its official Uniswap V4 pool. Read current on-chain state to select the route.

### Choose the route

| `Factory.graduations(token)` status | Meaning                                            | Available path                                                         |
| ----------------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------- |
| `0 — NotGraduated`                  | Curve reserves have not been swept                 | Curve trades while initialized, ungraduated and sellable tokens remain |
| `1 — Swept`                         | Graduation reserves are held for pool creation     | Create the official pool; Curve trading is closed                      |
| `2 — PoolCreated`                   | Official V4 liquidity is created                   | V4 swaps through a compatible router, with the Hook active             |
| `3 — EmergencyExited`               | Graduation reserves entered emergency distribution | Redeem through the activated EmergencyDistributor                      |

A sold-out Curve can still show NotGraduated if its automatic sweep failed. `AutoGraduationFailed` can accompany a successful purchase. Retry the sweep separately; do not treat the successful buy as proof of an active V4 pool. The [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation) table explains each action and failure state.

### Curve trading

Approve the input asset to the token's Curve, then use Exact Input buy/sell with minimum output and deadline. A closing buy can partially fill and refund unused Quote. See [Bonding Curve Trading](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/bonding-curve-trading) and the [cost overview](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims).

### V4 trading

Confirm PoolCreated, then read `poolForToken(token)`, `poolConfig(poolId)` and `isPoolActive(poolId)` from the configured Hook proxy. Check the token, Quote and pool identity.

The PoolKey sorts token and Quote into currency0/currency1 by address. Derive trade direction from that order. Exact Input fees reduce output; Exact Output fees increase input, and either launch tokens or Quote can be the fee asset.

The selected router must support the Hook's fee adjustment and enforce the user's final minimum output or maximum input. Follow that router's ERC20/Permit2 approval flow and simulate its final calldata. See [V4 Trading Integration](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/uniswap-v4-hooks/trading-integration).

While Swept, pool creation can be attempted or retried. If the timed recovery conditions become available, [Emergency Exit](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/emergency-exit) offers redemption instead. A progress percentage or failed swap alone does not establish which action is available.


---

# 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://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/trading-before-and-after-graduation.md?ask=<question>&goal=<user_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.
