> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/privacy-on-demand/networks.md).

# Networks

Privacy on Demand spans **two domains**:

1. **Host chain** — where your dApp contracts, assets, and the local **Inbox** live (for example Avalanche Fuji or Ethereum Sepolia).
2. **COTI** — where private computation runs via the **MPC executor** and the COTI-side **Inbox**.

The pages below list network parameters and deployed contract addresses for current test environments. Addresses can change after redeploys; treat [`deployConfig.json`](https://github.com/coti-io/pod-ecosystem-integration) (or your environment config), [`@coti-io/pod-sdk`](https://github.com/coti-io/coti-sdk-pod), and [`@coti-io/coti-contracts`](https://github.com/coti-io/coti-contracts) as the live source of truth when building against a specific release.

| Network                                                                        | Chain ID   | Role in PoD                                        |
| ------------------------------------------------------------------------------ | ---------- | -------------------------------------------------- |
| [COTI Testnet](/coti-documentation/privacy-on-demand/networks/coti-testnet.md) | `7082400`  | Private execution (MPC executor, COTI Inbox)       |
| [Avalanche Fuji](/coti-documentation/privacy-on-demand/networks/fuji.md)       | `43113`    | Host chain (dApp + Inbox paired with COTI Testnet) |
| [Ethereum Sepolia](/coti-documentation/privacy-on-demand/networks/sepolia.md)  | `11155111` | Host chain (dApp + Inbox paired with COTI Testnet) |

The shared CREATE3 **Inbox** address (`pod.inbox.v2.2`) is the same on every supported chain:

`0x3b8B70819f27e0438cBcE7f31894f799da52648F`

**Two Privacy Portal worlds**

| Portal                             | Where                                                         | Docs                                                              |
| ---------------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------- |
| **PoD cross-chain Privacy Portal** | Fuji / Sepolia factory + host pTokens; compute via COTI Inbox | Network pages above                                               |
| **Native COTI Privacy Portal**     | PrivateERC20 / bridges on COTI only                           | [COTI Privacy Portal](/coti-documentation/coti-privacy-portal.md) |

For general COTI chain RPC and faucet details (not PoD-specific), see the top-level [Networks](/coti-documentation/networks.md) section.


---

# 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.coti.io/coti-documentation/privacy-on-demand/networks.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.