Privacy on Avalanche
Privacy on Avalanche applies Privacy on Demand to Avalanche Fuji C-Chain (chain ID 43113): keep wallets, assets, and dApp contracts on Avalanche, and send encrypted private computation to COTI Testnet.
Fees on the host side are paid in AVAX. Private execution still happens on COTI; results return as ciphertext to your Fuji contracts for client-side decryption.
Development status: This Privacy on Avalanche material and the COTI PoD SDK it describes are under active development. Treat them accordingly: on-chain and client code may not yet be fully audited, and breaking changes (APIs, ABIs, addresses, presets, or documentation) can occur as the stack matures. Pin versions, follow release notes, and perform your own review before relying on anything in production.
Quick Access
Getting started on Avalanche Fuji (Day 0) — Wallet, faucet, Hardhat/Foundry, SnowScan smoke-test.
Tutorials: PoD dApps on Avalanche (choose your integration model) — Primitive-only vs custom COTI logic, then links to step-by-step Fuji guides.
Architecture and design — Inbox, MPC executor, PodUser, PodLib, and how they connect.
Avalanche Fuji network & addresses — Fuji C-Chain RPC, SnowScan, Inbox, Privacy Portal, and sample MpcAdder.
Networks — Fuji (host) + COTI Testnet (private execution) parameters.
Interactive PoD architecture on Fuji (pod.coti.io/avalanche) — Live demo: MpcAdder journey across Avalanche Fuji, relayer, and COTI.
Learn about fees — How PoA/PoD fees split across COTI and Fuji (paid in AVAX).
Millionaires demo — Live demo (includes an Avalanche Fuji route).
Further resources
Examples — Contract examples in
@coti-io/coti-contracts.PoD SDK documentation — Full SDK docs on GitHub.
General Privacy on Demand section — Multi-host PoD overview (not Avalanche-only).
This section is the Avalanche Fuji–first companion to Privacy on Demand: same PoD pattern, with Fuji C-Chain network constants, PodUserFuji presets, SnowScan explorers, and AVAX fee context. For integration, use @coti-io/pod-sdk (TypeScript) and @coti-io/coti-contracts (Solidity), plus the links below.
Fuji at a glance
Network
Avalanche Fuji C-Chain
Chain ID
43113
Native token
AVAX
RPC
https://api.avax-test.network/ext/bc/C/rpc
Explorer
Inbox
0x3b8B70819f27e0438cBcE7f31894f799da52648F
Private execution
COTI Testnet (7082400)
Solidity preset
PodUserFuji
Full tables: Avalanche Fuji.
Who this documentation is for
Product, compliance, and business readers
Plain-language model of privacy on Avalanche + COTI, where data lives, and what “async” private operations mean in practice.
Architects and technical leads
End-to-end diagrams for the Fuji ↔ COTI path, component roles, and domain boundaries.
Developers
Fuji-focused map from concepts to Solidity/TypeScript (PodUserFuji, AVAX fees, SnowScan), plus pointers to the authoritative SDK docs.
Table of contents
Start here
Getting started on Avalanche Fuji (Day 0) — Wallet, faucet, Hardhat/Foundry, SnowScan.
Understand first (readable without writing code)
What is Privacy on Avalanche? — Problem, promise, and constraints with Fuji as the host chain.
How a private request travels end to end — Timeline from user action on Fuji to decrypted result.
Architecture and main components — Where Inbox, MPC executor, PodUser, and PodLib sit, with diagrams.
Networks — Avalanche Fuji (host) and COTI Testnet (execution).
Glossary — Short definitions of terms you will see in PoD and SDK docs.
Deeper context
Async private operations (why it is not instant) — What “pending” means and why UX must reflect it.
How do PoA fees work? — Two-way Inbox budgets in AVAX, oracle conversion, and a worked gas-unit example.
For developers: mapping concepts to the SDK — Checklists and links to the PoD SDK documentation on GitHub.
Tutorials (hands-on)
Tutorials: building PoD dApps on Avalanche — When to use MpcLib / PodLib primitives vs custom COTI + Fuji contracts.
TypeScript PoD SDK (
CotiPodCrypto,PodContract) — Encryption/decryption, fee estimation, method calls, and request ID extraction.Cookbook: private investor allocations with PoD — Start from a familiar public Fuji allocation dApp, then make allocation reads and withdrawals private with PoD.
Tutorial: private Adder on Avalanche Fuji — Minimal primitive-only adder:
PodUserFuji, AVAX fees, TypeScript crypto.Tutorial: custom privacy logic with PoD — Encrypted messaging shape:
DirectMessageCotiSide+ Fuji orchestrator.
Official technical reference
The machine-readable contracts, types, and APIs live in the open-source SDK. Treat this book chapter as the human-oriented companion; treat the repository as the source of truth for signatures, fees, and network constants:
Last updated
Was this helpful?