What it does
On a public chain, paying someone can expose far more than the payment: an observer can often read the sender's remaining balance, past transactions and counterparties. No bank account works that way. This module is designed so a balance is held as encrypted notes rather than a readable number against an address, transfers are proved correct with zero-knowledge proofs instead of being published in the clear, and each payment can be sent to a fresh destination derived for the recipient under the ERC-5564 stealth-address standard. The recipient sees the payment they received; they do not see what else the sender holds. It is designed as the confidential layer of SBX AURA and is in development.
Powers
How it works
Confidential Payments sits between the account and the rail. Smart Accounts authorise the payment, Selective Disclosure decides who may later read it, and the Settlement Engine moves the value.
Select a step to replay it. Hover to pause.
Step 1 of 3: Hold. A balance is held as encrypted notes rather than a public number attached to an address.
Key capabilities
Encrypted-note balances
Value is held as notes only the owner can identify, rather than a readable balance against a public address.
Zero-knowledge transfers
The network verifies that a transfer is valid without being told the sender, recipient or amount.
Stealth receiving addresses
Each payment can go to a fresh destination derived for the recipient, so one reusable public address is not exposed.
Confidential, not anonymous
Compliance screening still runs, and authorised parties can be granted visibility. This is confidentiality with accountability.