Privacy on Demand

Privacy on Demand lets applications use strong privacy for data and computation while still using ordinary EVM chains (Ethereum, L2s, and other compatible networks) for accounts, assets, and business workflows.

Development status: This Privacy on Demand 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

• Tutorials: PoD dApps (choose your integration model) — Primitive-only vs custom COTI logic, then links to step-by-step guides.

• Architecture and design — Inbox, MPC executor, PodUser, PodLib, and how they connect.

• Learn about fees — How PoA/PoD fees split across COTI and your host chain.

• Millionaires demo — Live demo (external).

Further resources

• Examples — Contract examples in the PoD SDK repo.

• PoD SDK documentation — Full SDK docs on GitHub.

The same Quick Access and Further resources blocks appear on the docs homepage.

---

This section explains what PoD is, how it feels to users and operators, and how the main pieces fit together. For step-by-step integration with the COTI PoD SDK, use the npm package, the documentation on GitHub, and the links below.

Who this documentation is for

Audience	What you will get here
Product, compliance, and business readers	Plain-language model of privacy, where data lives, and what “async” private operations mean in practice.
Architects and technical leads	End-to-end diagrams, component roles, and boundaries between chains and domains.
Developers	A clear map from concepts to Solidity/TypeScript work, plus pointers to the authoritative SDK docs.

Table of contents

Understand first (readable without writing code)

1. What is Privacy on Demand? — Problem, promise, and constraints in everyday language.

2. How a private request travels end to end — Timeline from user action to decrypted result.

3. Architecture and main components — Where Inbox, MPC executor, PodUser, and PodLib sit, with diagrams.

4. Glossary — Short definitions of terms you will see in PoD and SDK docs.

Deeper context

1. Async private operations (why it is not instant) — What “pending” means and why UX must reflect it.

2. How do PoA fees work? — Two-way Inbox budgets, oracle conversion, and step-by-step gas-unit consumption (worked example).

3. For developers: mapping concepts to the SDK — Checklists and links to the PoD SDK documentation on GitHub.

Tutorials (hands-on)

1. Tutorials: building PoD dApps — When to use MpcLib / PodLib primitives vs custom COTI + host contracts, with links to focused walkthroughs.

2. TypeScript PoD SDK (CotiPodCrypto, PodContract) — Encryption/decryption, fee estimation, method calls, and request ID extraction.

3. Cookbook: private investor allocations with PoD — Start from a familiar public Sepolia allocation dApp, then make allocation reads and withdrawals private with PoD.

4. Tutorial: private Adder on Sepolia — Minimal primitive-only adder: PodUserSepolia, fees, TypeScript crypto.

5. Tutorial: custom privacy logic with PoD — Encrypted messaging shape: DirectMessageCotiSide + Sepolia 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:

• COTI PoD SDK — documentation index