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

# Avalanche Fuji

Avalanche Fuji C-Chain is the **primary host chain** for this Privacy on Avalanche section. Your dApp contracts and the local **Inbox** live here; fees are paid in **AVAX**; private computation still runs on [COTI Testnet](/coti-documentation/privacy-on-avalanche/networks/coti-testnet.md).

Use the Solidity preset **`PodUserFuji`** (or configure the Inbox + COTI executor manually) so Fuji dApps route to COTI Testnet chain ID `7082400`.

> **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   | Avalanche Fuji C-Chain                       |
| Chain ID       | `43113`                                      |
| Currency       | AVAX                                         |
| RPC URL        | `https://api.avax-test.network/ext/bc/C/rpc` |
| Block explorer | <https://testnet.snowscan.xyz>               |

Private execution for Fuji dApps targets **COTI Testnet** (`7082400`). See [COTI Testnet](/coti-documentation/privacy-on-avalanche/networks/coti-testnet.md) for the MPC executor and COTI-side Inbox.

## PoD contracts

| Contract           | Address                                                                                                                         | Description                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Inbox              | [`0x3b8B70819f27e0438cBcE7f31894f799da52648F`](https://testnet.snowscan.xyz/address/0x3b8B70819f27e0438cBcE7f31894f799da52648F) | Cross-chain message router (CREATE3; same address on every PoD chain) |
| Price oracle       | [`0x95ce33378c88734f3d86b51a4c6dc588722995fd`](https://testnet.snowscan.xyz/address/0x95ce33378c88734f3d86b51a4c6dc588722995fd) | Local/remote token prices used by Inbox fee conversion                |
| MpcAdder (example) | [`0x8b7d9e70477aabe68500b72acb7f367993edde39`](https://testnet.snowscan.xyz/address/0x8b7d9e70477aabe68500b72acb7f367993edde39) | Reference primitive-only adder dApp on Fuji                           |

## PoD cross-chain Privacy Portal (Fuji)

This is the **PoD host-chain Privacy Portal** (factory + pTokens on Fuji, private compute via COTI Inbox). It is **not** the [native COTI Privacy Portal / PrivateERC20](/coti-documentation/coti-privacy-portal.md) that runs entirely on COTI.

| Contract                 | Address                                                                                                                         |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| Privacy Portal factory   | [`0xaf9327277cb370d536d2c8a9e15a0a7ff6c42c15`](https://testnet.snowscan.xyz/address/0xaf9327277cb370d536d2c8a9e15a0a7ff6c42c15) |
| Portal implementation    | [`0xf4fb32758e41c1b465049c5c967a6604b6c28dce`](https://testnet.snowscan.xyz/address/0xf4fb32758e41c1b465049c5c967a6604b6c28dce) |
| Pod token implementation | [`0x1c0b982e084451e0b272cddcce902b04c679317d`](https://testnet.snowscan.xyz/address/0x1c0b982e084451e0b272cddcce902b04c679317d) |

### Privacy Portal tokens

| Token   | Underlying                                   | Portal                                       | pToken                                       |
| ------- | -------------------------------------------- | -------------------------------------------- | -------------------------------------------- |
| p.MTT   | `0x328e70e1c52662cd5f19f824fcb8b463d77a6686` | `0x758a8F9a216A95773DDf6F73004B85d59f224518` | `0x02f284a1968160E1d3e4bC2BA3261be49725E765` |
| p.USDC  | `0x5425890298aed601595a70AB815c96711a31Bc65` | `0xE75373ADb4AD1A5634a10f4644822943830b18c5` | `0x21576D8CCE47d044C5815bd59eca1F6DA94c65A5` |
| p.WAVAX | `0xd00ae08403B9bbb9124bB305C09058E32C39A48c` | `0xe6932f6Ab846bf389f7ef355dd5830594623B8E5` | `0x74d47cD68203066c97BA99787Fe1e0c68Ce42b04` |

## How this network fits PoD

| Piece        | Role on Fuji                                                                                                                                                 |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Inbox        | Host-side courier: accepts encrypted requests from your dApp and delivers COTI callbacks                                                                     |
| Your dApp    | Configures Inbox + COTI chain ID `7082400` + [MPC executor on COTI Testnet](/coti-documentation/privacy-on-avalanche/networks/coti-testnet.md#pod-contracts) |
| Price oracle | Converts Fuji fee budgets against COTI-side costs                                                                                                            |

Flow at a glance: **user / dApp on Fuji → Fuji Inbox → (relayer) → COTI Inbox → MPC executor → callback to Fuji**.

## SDK constants

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

| Constant        | Value                                                                       |
| --------------- | --------------------------------------------------------------------------- |
| Chain ID        | `43113` (`AVALANCHE_FUJI_CHAIN_ID`)                                         |
| Inbox           | `0x3b8B70819f27e0438cBcE7f31894f799da52648F` (`FUJI_DEFAULT_INBOX_ADDRESS`) |
| Solidity preset | `PodUserFuji` — sets Fuji Inbox and configures COTI Testnet MPC executor    |

Point `configureCoti` at the [COTI Testnet MPC executor](/coti-documentation/privacy-on-avalanche/networks/coti-testnet.md#pod-contracts) and chain ID `7082400` if you are not using `PodUserFuji`.

## Getting Fuji AVAX and exploring txs

Step-by-step wallet, faucet, and toolchain setup: [**Getting started on Avalanche Fuji (Day 0)**](/coti-documentation/privacy-on-avalanche/getting-started-fuji.md).

* Fund a wallet with **test AVAX**, then deploy and call your dApp with enough `msg.value` for two-way Inbox fees.
* Verify contracts and transactions on [SnowScan testnet](https://testnet.snowscan.xyz).
* Hands-on next step: [Tutorial: private Adder on Avalanche Fuji](/coti-documentation/privacy-on-avalanche/tutorial-private-adder-fuji.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coti.io/coti-documentation/privacy-on-avalanche/networks/fuji.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.