Arc is building opt-in privacy so you can design financial applications that keep sensitive data confidential while still meeting compliance and audit requirements. Most blockchains are fully transparent — every address and amount is public. Arc takes a middle path: transactions are public by default, and participants can opt in to privacy when business needs require it. You can design your application with selective disclosure in mind today — no changes to the core transaction model will be required when privacy features become available.Documentation Index
Fetch the complete documentation index at: https://docs.arc.io/llms.txt
Use this file to discover all available pages before exploring further.
Privacy features are on the roadmap and not yet available on Arc.
Confidential transfers
Fully transparent ledgers expose amounts that businesses need to keep private, such as payroll, trade finance, and B2B invoices. Arc addresses this with confidential transfers:- Transaction amounts are encrypted and not visible on the public ledger.
- Sender and receiver addresses remain visible for compatibility with analytics and monitoring tools.
- Transactions finalize onchain with the same deterministic guarantees as public transfers.
Selective disclosure with view keys
View keys let you grant controlled read access to confidential transaction data. Auditors and regulators can review encrypted details when required, and institutions can monitor their own customer activity. This lets you meet regulatory obligations such as the Travel Rule while still protecting sensitive business logic.Modular privacy architecture
Arc’s privacy system is modular. It starts with Trusted Execution Environments for their performance characteristics and is designed to support additional cryptographic backends as they become production-ready.| Backend | Status | Description |
|---|---|---|
| TEE (Trusted Execution Environments) | Initial backend | Processes confidential data in hardware-isolated enclaves for high throughput. |
| MPC (Multi-Party Computation) | Planned | Splits secrets across multiple parties so no single entity can reconstruct sensitive data. |
| FHE (Fully Homomorphic Encryption) | Planned | Runs computations directly on encrypted data without decrypting it first. |
| ZK (Zero-knowledge proofs) | Planned | Proves a statement is true without revealing the underlying data. |