> For the complete documentation index, see [llms.txt](https://docs.zama.org/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zama.org/protocol/confidential-swap/reference/addresses.md).

# Contract addresses

The ConfidentialSwap proxy address per network, and how to read pairs, fees, and the market-maker set from chain.

The `ConfidentialSwap` proxy, per network. This is the only address you need to integrate — it is the stable entry point, and its implementation can be upgraded behind it.

| Network  | Chain id | `ConfidentialSwap`                                                                                                                    | Status |
| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------ |
| Ethereum | 1        | [`0x8Fe22dC7e624c02b1805d41E09741490E1018C01`](https://eth.blockscout.com/address/0x8Fe22dC7e624c02b1805d41E09741490E1018C01)         | live   |
| Sepolia  | 11155111 | [`0xab86445f72A64A99C8d248dcE004915B45C88e20`](https://eth-sepolia.blockscout.com/address/0xab86445f72A64A99C8d248dcE004915B45C88e20) | live   |

## Compliance address

The address configured with decryption rights over every confidential value in the protocol — see [Compliance access](/protocol/confidential-swap/protocol/confidentiality.md#compliance-access). Í

| Network  | Compliance address                                                                                                            |
| -------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Ethereum | [`0x9b828219ad863491eb9b5225aE2d133eEDEa9B71`](https://eth.blockscout.com/address/0x9b828219ad863491eb9b5225aE2d133eEDEa9B71) |

## Everything else is on-chain state

Pairs, fees and the market-maker set change without a redeployment, so read them from the contract rather than from a page that can go stale:

| What                    | How                                                |
| ----------------------- | -------------------------------------------------- |
| Active pairs            | `getActivePairIds()`, then `getPair(pairId)`       |
| A pair's assets and fee | `getPair(pairId)` → `{ asset0, asset1, feeShift }` |
| The market-maker set    | `getRoleMembers(MARKET_MAKER_ROLE())`              |
| Maximum auction windows | `maxQuotingPeriod()` · `maxSettlementPeriod()`     |

Confidential token addresses are published with the token documentation rather than duplicated here — `getPair` resolves them for any active pair anyway. For example, cUSDC's address is published in the [Confidential Vaults](https://docs.zama.org/protocol/confidential-vault) documentation.


---

# 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.zama.org/protocol/confidential-swap/reference/addresses.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.