> 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/uniswap-v4-hooks/overview-and-pool-structure.md).

# Overview and Pool Structure

An official Pro pool pairs the launch token with its configured ERC20 Quote asset. After the reserve sweep reaches Swept, `Factory.createGraduatedPool(token)` creates and funds that pool and activates its Hook.

## Discover the pool

Read `poolForToken(token)` on the configured Hook proxy. Pass that ID to `poolConfig(poolId)` and `isPoolActive(poolId)` on the same proxy. Confirm the token, Quote, tick spacing and active status against the Factory record.

The pool's identity is its complete PoolKey:

| Field                    | Pro rule                                  |
| ------------------------ | ----------------------------------------- |
| `currency0`, `currency1` | Launch token and Quote, sorted by address |
| `fee`                    | `0` for the current official Hook pool    |
| `tickSpacing`            | The launch's snapshotted setting          |
| `hooks`                  | MemeHookV2 proxy address                  |

`fee=0` is the pool's fee field. The Hook still charges its base fee and Creator Tax; see [Hook Behavior and Fees](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/uniswap-v4-hooks/hook-behavior-and-fees).

Pool preparation precedes liquidity creation and activation. Confirm PoolCreated and active Hook state before routing a swap; a preparation event alone is insufficient.

## Graduation liquidity

Pool creation initializes the price and supplies full-range liquidity. LaunchLocker permanently holds the protocol's position and residual launch tokens. It offers no withdrawal, liquidity-removal or fee-collection flow. Quote rounding dust goes to the configured protocol recipient.

These locks describe the protocol's graduation position. Independent liquidity positions retain their own ownership, and the Hook implementation remains subject to its upgrade permissions.

For state transitions and failed-attempt behavior, see [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation). For amounts, authorization and final router limits, continue with [Trading Integration](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/uniswap-v4-hooks/trading-integration).


---

# 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/uniswap-v4-hooks/overview-and-pool-structure.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.
