Confidentiality on
@Aptos now spans three opt-in layers, all live on mainnet. Each targets a different part of what's visible onchain, and each opens up something new for builders.
Identity: Keyless Accounts
• Users create and manage Aptos accounts with existing credentials like Google or Apple, verified with zero-knowledge proofs, without publicly tying that identity to an onchain address.
• What it enables: apps that onboard users with a login they already have.
Amounts: Confidential APT
• Users can encrypt balances and transfer amounts. Validators check a zero-knowledge proof that a transfer is valid, while balances and amounts stay confidential. Senders and recipients remain visible onchain.
• What it enables: payments where amounts remain between the sender and the receiver, designed for compliant use cases.
Intent: Encrypted Mempool
• The payload (function called + arguments) is encrypted client-side, ordered while encrypted, and decrypted by validators together only after the block is finalized. Sender and gas fee stay visible.
• What it enables: traders can encrypt the orders they choose, designed to lower MEV risk on those orders, and agents can submit trades with inputs encrypted until execution.
Opt-in by design, built for compliant use.
Confidential APT is available in
@PetraWallet and on Confidential Assets Web. Encrypted Mempool is supported in Petra and on
@DecibelTrade, and developers can integrate it with the TypeScript SDK (v7.0.0+). Existing Move contracts need no changes.
Petra:
Confidential Assets Web:
Built by Aptos Labs.