Starknet Privacy is a protocol for private asset transfers on Starknet: sender, receiver, and amounts are hidden from outside observers, while validity is enforced with client-side zero-knowledge proofs (Stwo / Cairo). A compliance layer allows an auditing entity to trace activity when legally required, without exposing unrelated users.Documentation Index
Fetch the complete documentation index at: https://docs.starknet.io/llms.txt
Use this file to discover all available pages before exploring further.
What these docs are for
These docs describe the protocol—notes, channels, discovery, compliance, transaction ordering, and security considerations—so developers, partners, and enterprises can understand how Starknet Privacy works.- Live on mainnet: the privacy pool contract is deployed at
0x0403…812a. The contract source is readable on Voyager. - SDK not yet public: the TypeScript SDK and proving stack are not open sourced yet. When they ship, operational guides (install, quickstart, end-to-end usage) will be added here.
Why Starknet Privacy?
If you care about confidential transfers, you have probably seen mixers (fixed amounts, one-time use) or privacy chains that require a separate ecosystem. Starknet Privacy takes a different path:- Stay on Starknet — no new chain; access existing Starknet DeFi and accounts.
- Arbitrary amounts, reusable notes — no fixed denominations.
- Discovery that scales with you — recipients discover notes in time proportional to their own activity.
- Compliance by design — selective disclosure for lawful requests, without exposing unrelated users.
- One account for everything — existing Starknet account signs spends.
Comparison
For the latest maintained cross-protocol comparison grid, use privacygrid.dev.Note: this page keeps the protocol summary concise and defers detailed protocol-to-protocol scoring to the dedicated grid.
Resources
Paper
Scalable Compliant Privacy on Starknet (IACR ePrint 2026/474)
Protocol deep-dives
Architecture, flows, and cryptography in these docs
What you get
| Property | Summary |
|---|---|
| Private transfers | Sender, receiver, and amount hidden from observers; transacting parties and authorized auditors can see details. |
| Compliance | Designated auditor can selectively trace history under legitimate regulatory request. |
| Efficient discovery | Recipients find notes in time scaling with their activity, not total pool activity. |
| Multi-asset | One pool supports multiple token types. |
| DeFi | Anonymous interaction with existing Starknet DeFi via open notes and atomic flows. |
| Account abstraction | Spend authority uses your Starknet account (multisig, smart wallet, etc.). |
Next steps
Architecture
Pool, verifier, and high-level design
Transaction flow
Client actions and ordering