> 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-classic/core-features/uniswap-v4-hooks.md).

# Uniswap V4 Hooks

An Arc launch begins on a bonding curve. At graduation, its liquidity is seeded into an official Uniswap V4 pool that uses the shared MemeHook. This section covers pool initialization and trading after graduation. Token creation and pre-graduation pricing remain documented under Launchpad.

The Hook validates official pool initialization, charges swap fees and accounts for creator, protocol, buyback and Partner allocations. Applications trade through a Router and PoolManager; they do not call the Hook's swap callback themselves.

#### Integration paths

| You are building                        | Read                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A wallet or trading UI using Arc routes | [Aggregator Quickstart](https://docs.peach.ag/documentation/arc/aggregator/quickstart) and [Trading integration](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/trading-integration)                                                                                                                                                                                                  |
| A V4-aware Router or indexer            | [Pool structure](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/overview-and-pool-structure), [Hook behavior](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/hook-behavior-and-fees), [Partner hookData](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/partner-and-hookdata) |
| A creator revenue UI or fee operator    | [Fee settlement and state](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/fee-settlement-and-state)                                                                                                                                                                                                                                                                                   |

#### Three distinctions to preserve

* A `poolCreated` launch is not necessarily already routable by the Aggregator. The API must also index the pool and find sufficient liquidity.
* The official pool's core LP fee is zero, but the Hook can charge its swap fee and Creator Tax.
* Fees accrued in the Hook are pending. Only balances credited to FeeEscrow can be claimed.

The Arc Partner model and Begin/Settle/Finalize sweep process are specific to Arc. Do not substitute Pons contract names, event signatures or sweep methods when integrating these pools.

#### Network baseline

These guides use production Classic on Arc Mainnet (`5042`) with SDK `1.0.0`. Use the [production addresses](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/contract-address) and read each pool's current configuration before trading.

Continue with [Overview and pool structure](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/uniswap-v4-hooks/overview-and-pool-structure). For the transition from the curve, see [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-classic/core-features/graduation).


---

# 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-classic/core-features/uniswap-v4-hooks.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.
