> 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-avalanche/networks/coti-testnet.md).

# COTI Testnet

COTI Testnet is the **private execution** side of Privacy on Demand. Host-chain dApps on [Avalanche Fuji](/coti-documentation/privacy-on-avalanche/networks/fuji.md) send encrypted work through the cross-chain Inbox; COTI runs the private computation and returns encrypted results.

> **Note:** Addresses below match `pod-ecosystem-integration/deployConfig.json` (Inbox salt `pod.inbox.v2.2`). They may change after contract redeploys. Confirm against that file or your SDK release before production use.

## Network details

| Parameter      | Value                         |
| -------------- | ----------------------------- |
| Network name   | COTI Testnet                  |
| Chain ID       | `7082400`                     |
| Currency       | COTI                          |
| RPC URL        | `https://testnet.coti.io/rpc` |
| WebSocket URL  | `wss://testnet.coti.io/ws`    |
| Block explorer | <https://testnet.cotiscan.io> |
| Status         | <https://uptime.coti.io>      |

Also see the general COTI [TestNet](/coti-documentation/networks/testnet.md) page for MetaMask setup and the [Testnet faucet](/coti-documentation/networks/testnet/faucet.md).

## PoD contracts

| Contract         | Address                                                                                                                        | Description                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- |
| Inbox            | [`0x3b8B70819f27e0438cBcE7f31894f799da52648F`](https://testnet.cotiscan.io/address/0x3b8B70819f27e0438cBcE7f31894f799da52648F) | Cross-chain message router (CREATE3; same address on every PoD chain)                   |
| MPC executor     | [`0x6804961167c3c8ef2bf6839ddcf51ec1fbe800c3`](https://testnet.cotiscan.io/address/0x6804961167c3c8ef2bf6839ddcf51ec1fbe800c3) | Entry point for library-style private operations (`configureCoti` target on host dApps) |
| Price oracle     | [`0xb471e172876ba9bb24a43528779ea31e0b0bda2f`](https://testnet.cotiscan.io/address/0xb471e172876ba9bb24a43528779ea31e0b0bda2f) | Local/remote token prices used by Inbox fee conversion                                  |
| Pod ERC20 mother | [`0xaeb2271959031b65cba63302cff5d970b49d4a7b`](https://testnet.cotiscan.io/address/0xaeb2271959031b65cba63302cff5d970b49d4a7b) | COTI-side registry for **PoD cross-chain** Privacy Portal / pToken flows                |

> **Portal labeling:** The mother / pToken path above is for **PoD cross-chain Privacy Portal** (host chain Fuji ↔ COTI). For the **native COTI Privacy Portal** (PrivateERC20 on COTI only), see [COTI Privacy Portal — contract addresses](/coti-documentation/coti-privacy-portal/developer-guide/contract-addresses.md).

## Protocol helpers (COTI Testnet)

These are not PoD-specific, but most PoD clients need them for account onboarding and chain tooling:

| Contract                  | Address                                                                                                                        |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| AccountOnboard            | [`0x536A67f0cc46513E7d27a370ed1aF9FDcC7A5095`](https://testnet.cotiscan.io/address/0x536A67f0cc46513E7d27a370ed1aF9FDcC7A5095) |
| MPCInterface (precompile) | `0x0000000000000000000000000000000000000064`                                                                                   |

Full COTI Testnet protocol addresses: [Contracts Addresses](/coti-documentation/networks/testnet/contracts-addresses.md).

## How this network fits PoD

| Piece        | Role on COTI Testnet                                                          |
| ------------ | ----------------------------------------------------------------------------- |
| Inbox        | Receives mined requests from host chains and routes callbacks back            |
| MPC executor | Target address host dApps pass to `configureCoti(..., COTI_TESTNET_CHAIN_ID)` |
| Price oracle | Converts fee budgets between host gas units and COTI                          |

Typical pairing for this section:

* **Host:** [Avalanche Fuji C-Chain](/coti-documentation/privacy-on-avalanche/networks/fuji.md) · **Execution:** COTI Testnet (see the [private Adder tutorial](/coti-documentation/privacy-on-avalanche/tutorial-private-adder-fuji.md))

## SDK constants

In `@coti-io/pod-sdk` and `@coti-io/coti-contracts`:

| Constant | Value                                                                               |
| -------- | ----------------------------------------------------------------------------------- |
| Chain ID | `7082400`                                                                           |
| Inbox    | `0x3b8B70819f27e0438cBcE7f31894f799da52648F` (`COTI_TESTNET_DEFAULT_INBOX_ADDRESS`) |

Confirm the MPC executor against your deployed release — presets in `PodNetworkConstants` can lag a redeploy; wire the address from the table above (or your env) in `configureCoti`.


---

# 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-avalanche/networks/coti-testnet.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.