Apply privacy as you need it
Control visibility rules for activity, without trading off auditability
The cost of the trust paradox
Standard blockchains are public by default. For organizations handling sensitive data, that "feature" becomes an operational and regulatory risk.
No selective disclosure
Traditional blockchains force all-or-nothing visibility: fully public, fully private, or offchain without verifiability.
The compliance deadlock
Proving eligibility requires exposing sensitive data, forcing a tradeoff between privacy and compliance.
Retreat to centralization
Privacy needs push systems offchain, sacrificing transparency, verifiability, and trust guarantees.
Design who sees what, and when
Prove without revealing
Use zero-knowledge proofs to verify identity or facts without exposing underlying data.
Set visibility rules
Define who can access what data, with selective disclosure that remains enforceable and auditable.
Keep data private, still verifiable
Encrypt data at the source while preserving verifiable proofs of correctness, ownership, or eligibility.
Compute privately, verify onchain
Run confidential computation offchain and return attestations that smart contracts can verify onchain.
Enforce compliance without gatekeepers
Apply compliance rules onchain while preserving privacy, without relying on centralized intermediaries.
Reusable patterns you can compose into real workflows
Contextual privacy
Combine confidential state and selective disclosure so each participant sees only their relevant view.
Data minimization at default
Store minimal onchain data; keep sensitive data encrypted offchain with verifiable ZK proofs.
Encrypted data and selective disclosure
Encrypt data at source with policies enabling role-based, time-bound, revocable disclosure.
Alkimi uses Seal so Walrus ad impression files are visible only to authorized publishers and advertisers.
Verifiable offchain computation
Run confidential logic in TEEs and return attestations smart contracts can verify onchain.
Sui Sentinel runs logic in Nautilus Enclaves and submits signed results for onchain verification.
Verifiable workflows
Combine private state and proofs to meet audit and compliance requirements without exposing data.
ATHEX uses ZK proofs to validate reserves and bids without revealing positions or amounts.
Primitives and protocols that implement programmable privacy
zkLogin
Enables social sign-in while keeping passwords and personal info hidden and preventing cross app tracking.
zkproofs
Validates key data such as eligibility and ownership without revealing confidential or sensitive data.
Passkey
Uses biometrics, PIN, or hardware keys to approve actions without sharing secrets with apps.
Seal
Encrypt sensitive data and enforce role-based, time-bound, auditable access so only the right parties can decrypt.
Nautilus
Run confidential logic in secure TEEs and return certified outcomes that smart contracts can verify onchain.