> 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/contract-address.md).

# Contract Address

Arc mainnet Hook deployments, example PoolKeys, PoolManager and Quoter.

### Deployment scope

The recorded deployments below are for **Arc mainnet (Chain ID 5042)**. Verify runtime code, PoolManager binding, configuration and feature support at an explicit block before use. Contract behavior in this guide is pinned to [314ed2151367d3edb6f9045f05f5eb18567f5aa6](https://github.com/peachbuild/adaptive-pools/tree/314ed2151367d3edb6f9045f05f5eb18567f5aa6). The Arc references come from integration guide v1.1. The Quoter records the historical reference-comparison endpoint; verify its current deployment and execution support separately.

SDK examples use `marketArcMainnet` from `@masterpeach/market-sdk@1.0.1` (`deploymentId: arc-mainnet-20261021`). The preset includes addresses, runtime hashes and bindings; do not reconstruct it from this abbreviated table or mix it with another deployment. Run `verifyDeployment()` explicitly; use `prepare: true` for funds operations. Earlier contract-reference behavior remains pinned to the source above; see [Overview](https://docs.peach.ag/documentation/arc/adaptive-pools/overview#version-scope).

### Contract roles

| Contract              | Integration role                                                                                                                                                     |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hook (Ramp / RwaRamp) | Selects swap fees and exposes direct range-share liquidity and claim methods.                                                                                        |
| PoolManager           | Stores V4 AMM state; a compatible router unlocks it, swaps and settles currency deltas.                                                                              |
| Quoter                | Simulates a selected-pool swap using eth\_call. Quoting does not transfer funds or reserve execution.                                                                |
| Router                | Spender and settlement entry point for the selected transaction flow. Verify its deployment separately; do not substitute a Quoter or helper address as the spender. |

### Arc Hook deployments

| Chain ID | Hook type | Hook address                                 | Sample PoolId                                                        |
| -------- | --------- | -------------------------------------------- | -------------------------------------------------------------------- |
| 5042     | Ramp      | `0x8c960De62a26A688B72e6cbf644F46715642a080` | `0x2e6e7f11473f1534c44954c6ff96848bf950ec20078686bd2e5f894893fbe560` |
| 5042     | RwaRamp   | `0x3722d2840bFA4E9610d265DA08078d178bF46080` | `0xc026ead7a7ba825083b0b88fe362c35cdfbb0095ac7ae702c84273822ca85618` |

### PoolManager and example PoolKeys

Arc PoolManager: `0x8366a39CC670B4001A1121B8F6A443A643e40951`.

Both example PoolKeys use dynamic fee `0x800000` (8388608) and tickSpacing **10**. Preserve the exact ordered currencies below.

| Chain / type   | currency0: address (decimals)                            | currency1: address (decimals)                             |
| -------------- | -------------------------------------------------------- | --------------------------------------------------------- |
| 5042 / Ramp    | cirBTC: `0x171a4217b86a807a64eb94757db6849fb4bdbaa0` (8) | USDC: `0x3600000000000000000000000000000000000000` (6)    |
| 5042 / RwaRamp | tUSD: `0xb01702df2b75353d245bbe8c697c3152726dac21` (18)  | tSTOCK: `0xb44ff1febfdd975e881fea3170f4e0ff0cba8638` (18) |

Labels identify sample assets, not guarantees about issuer or economic properties. Token addresses are authoritative. No native-currency Hook is included in this Arc deployment set.

### Quoter addresses

| Chain    | Quoter used by the reference comparisons     |
| -------- | -------------------------------------------- |
| Arc 5042 | `0x8Dc178eFB8111BB0973Dd9d722ebeFF267c98F94` |

See [State Reads and Quoting](https://docs.peach.ag/documentation/arc/adaptive-pools/core-features/state-reads-and-quoting) for the tuple ABI and eth\_call behavior. SDK and source links are maintained in [Resources](https://docs.peach.ag/documentation/arc/adaptive-pools/overview#resources).

### SDK approval targets

Direct LP deposits approve `key.hooks`. ZapIn uses `getZapInSpendStatus().data.spender` (the current LiquidityRouter); a Helper is never an approval target. ERC-20 swaps need token → Permit2 and Permit2 → the configured swap Router allowances; read their addresses with `getSwapSpendStatus`. Confirm every approval, then refresh the quote. Do not reuse a spender or signed plan from another Router deployment.

Use `getPool` / `listPools` for current registered PoolKeys. The rows above are sample identities, not proof of current Registry admission, liquidity, asset authenticity or execution readiness. The production `marketTestPools` catalog is empty.


---

# 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/contract-address.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.
