> 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/adaptive-pools/overview.md).

# Overview

Dynamic fees, range liquidity and earnings for Uniswap V4 integrations.

Peach Adaptive Pools combine Uniswap V4 liquidity with dynamic LP fees. A pool can use a flat policy or an RWA calendar, with directional premiums, keeper updates and an optional Mid-block fee. LPs provide liquidity within a price range and receive a share of the trading fees earned by that range.

### Choose your integration

| Goal                                 | Start here                                                                                                                                                                   |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Quote and execute a swap             | [Quickstart](https://docs.peach.ag/documentation/arc/adaptive-pools/quickstart) — discover a pool, pin the execution context, request a quote and prepare router settlement. |
| Add or remove liquidity              | [Providing Liquidity](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/providing-liquidity)                                                              |
| Read earnings and claim fees         | [Fees & Claims](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/fees-and-claims)                                                                        |
| Reproduce fee and quotation behavior | [Core Features](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features) — fees, RWA calendars, Mid-block observations, state reads and integration checks.     |

Swaps use normal V4 discovery, quoting and router settlement. Peach Registry registration and LP-share integration are not required by the direct swap path. SDK pool discovery uses its configured Registry; keep these integration paths distinct. A discovered pool still needs valid configuration, initialized state, available liquidity and an executable route. For the pinned direct-contract flow, also check pause state.

For direct-contract integrations using the pinned reference version:

1. Discover a pool: read PoolManager initialization events and verify the PoolKey, supported Hook, pool configuration and initialized state.
2. Quote with the current fee: resolve the policy for the swap direction and execution timestamp, then run normal V4 swap math or use the chain Quoter. RWA sessions, keeper expiry and earlier swaps in the execution block can change the result.
3. Execute through a compatible V4 router: unlock PoolManager, call swap, settle input deltas and take output deltas. Hook data can be empty. Re-quote when needed and enforce the accepted minimum output or maximum input and deadline.

The protocol guides also support direct integrations with a compatible V4 router, Quoter and the pinned contract ABIs. Pool quoting and swap submission remain separate operations.

### Pool types

| Hook                         | Contract  | Fee policy and supported assets                                       |
| ---------------------------- | --------- | --------------------------------------------------------------------- |
| PeachAdaptivePoolDefaultHook | `Ramp`    | ERC20/ERC20; flat autonomous base plus directional premium.           |
| PeachAdaptivePoolRWAHook     | `RwaRamp` | ERC20/ERC20; calendar-based autonomous base plus directional premium. |

The documented Arc deployment set includes Ramp and RwaRamp. No Arc native Hook is included in that set. See [Contract Address](https://docs.peach.ag/documentation/arc/adaptive-pools/contract-address) for exact identities and example PoolKeys.

### Version scope

The contract-specific rules in these pages are checked against source commit `314ed2151367d3edb6f9045f05f5eb18567f5aa6`. Verify the target deployment and its current settings before use.

Read deployment settings at one explicit block. Recorded snapshots are historical evidence, and the pinned contract source governs if any description differs. See [Integration Checklist](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/validation-and-examples) for fixed-block comparisons and execution acceptance.

SDK examples follow `@masterpeach/market-sdk@1.0.1` and reviewed `main@b5fc5ba`, using `marketArcMainnet` and ABI provenance `53cb71c7ebcee257bd74e7d4c995e8db43e33187`. [Quickstart](https://docs.peach.ag/documentation/arc/adaptive-pools/quickstart) owns initialization, explicit `prepare: true`, deployment verification and safe submission. The older `314ed215` direct-contract reference has different pause/withdrawal behavior; use matching ABIs and verify the actual deployment. Installation does not certify or enable a funds operation.

### Resources

| Resource                             | Link                                                                                                                                                                                                                          |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SDK package and API README           | [@masterpeach/market-sdk](https://www.npmjs.com/package/@masterpeach/market-sdk)                                                                                                                                              |
| SDK source                           | [peach-ts-sdk / packages/market](https://git.techpilots.org/web/peach/peach-ts-sdk/-/tree/b5fc5bacdbee2364128044a4afe793682fa323f4/packages/market) — repository access required; reviewed main source; package version 1.0.1 |
| Contract source                      | [adaptive-pools — pinned source](https://github.com/peachbuild/adaptive-pools/tree/314ed2151367d3edb6f9045f05f5eb18567f5aa6)                                                                                                  |
| Deployments and chain infrastructure | [Contract Address](https://docs.peach.ag/documentation/arc/adaptive-pools/contract-address) — Arc deployments, example PoolKeys, PoolManager and Quoter.                                                                      |
| Official SDK releases                | [Changelog](https://docs.peach.ag/documentation/arc/adaptive-pools/changelog) — documentation versions and the scope of their verification evidence.                                                                          |


---

# 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/adaptive-pools/overview.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.
