> 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/core-features.md).

# Core Features

Trading fees, liquidity, earnings and contract integration references.

Use the feature pages below for contract behavior and integration requirements. Each topic has one primary reference; the [Quickstart](https://docs.peach.ag/documentation/arc/adaptive-pools/quickstart) covers the first swap and [Contract Address](https://docs.peach.ag/documentation/arc/adaptive-pools/contract-address) provides deployment identities.

### Trading and fees

| Feature                                                                                                                                     | What you will find                                                       |
| ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| [Fees](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/fees-and-keeper-policy)                                         | Fee categories, pips, direction, keeper resolution and caps.             |
| [RWA Calendar and Fee Curve](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/rwa-calendar-and-fee-curve)               | Sessions, opening and closing curves, holidays and exact calendar rules. |
| [Mid-block Policy and Observations](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/mid-block-policy-and-observations) | Optional same-block surcharge, reference prices and simulation state.    |

### Liquidity and earnings

| Feature                                                                                                         | What you will find                                                        |
| --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [Providing Liquidity](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/providing-liquidity) | Range shares, deposits, withdrawals, amount bounds and pause behavior.    |
| [Fees & Claims](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/fees-and-claims)           | Net earnings, protocol share, fee caps, claims and delegated permissions. |

### Integration reference

| Feature                                                                                                                 | What you will find                                                         |
| ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| [State Reads and Quoting](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/state-reads-and-quoting) | Hook interfaces, block-pinned reads, discovery, Quoter calls and rounding. |
| [Integration Checklist](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/validation-and-examples)   | Acceptance scenarios and executable fee examples.                          |

Adaptive Pools use standard V4 swap math and settlement. The Hook selects the LP fee; the pool still calculates token deltas through the normal price and tick traversal.

Both documented Hook variants enable only beforeInitialize and beforeSwap, permission bits 0x2080. There are no custom before-swap deltas and no after-swap callback. beforeSwap returns executionFee | 0x400000 as the LP fee override, with zero custom delta. Strip the override flag before using the rate in swap math.


---

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