Confidential accounts
Your balance, activity and transfers on USD Network are private. Receipts prove a payment, and the hourly proof of balances shows every balance is counted.
Every account on USD Network is confidential. Your balance, your activity and who you pay are visible to you, in the wallet, and to nobody else on the network. The public explorer shows that a transfer happened, when, and the block that sealed it. It never shows who sent it, who received it or how much.
The ledger is still checkable by anyone: every transaction is sealed into a signed block and the public log, witnesses cosign it and it is anchored on Solana, and every hour the sequencer signs a proof of balances whose total must equal the supply.
What is private and what is public
| Who can see it | |
|---|---|
| Your balance and nonce | You (signed with your key). USD.NET, as the operator |
| Your activity: who you paid, who paid you, amounts, memos | You, the other party. USD.NET, as the operator |
| That a transaction exists: its hash, time, block, fee | Everyone |
| A deposit or withdrawal: amount and the other chain's transaction | Everyone (it's public on that chain anyway). Never your USD Network address |
| Freezes and unfreezes, with the address and reason | Everyone, in the compliance log |
| Total supply, sum of all balances, bridged supply, vault balances | Everyone |
A transaction's public hash covers a random 16-byte salt and, for transfers, the sender's signature. Without them the hash can't be matched to a guessed sender, recipient or amount.
How your wallet reads your account
The network answers an account's own reads only when they are signed with its key. Your wallet signs a short read pass (it lasts at most 15 minutes and the wallet renews it) with the same key that signs your transfers. Only the signature leaves the browser. Developers can do the same: see Confidential reads.
Receipts
To show someone a payment, open it in Activity. Each line opens its receipt in the explorer: a link whose part after # carries the transaction's own fields. Browsers never send that part to a server. The explorer hashes the fields in your browser and shows them only if they match the transaction's public hash, and checks the sender's signature. So a receipt can't be edited or forged, and it shows nothing else about either account.
Verify your balance
Settings → Your account is Confidential → Verify my balance. The wallet fetches its leaf (balance and salt) in the latest snapshot and the sibling hashes and sums on the way to the root, rebuilds the root and total in your browser, and checks them against the snapshot the sequencer signed. It also shows whether the sum of every balance equals the supply. No other account's address is ever sent to you.
Who else can see accounts
USD.NET runs the sequencer, so, like a bank, it can see every account. It discloses account data only where the law requires it, through lawful requests. An auditor can be given read access with its own key. Hiding accounts from the operator too would take encrypted balances with zero-knowledge proofs or a sequencer inside a secure enclave; both are on the roadmap, not live.
What happens on other chains stays public there: a deposit into a USD Bridge vault and a withdrawal to an outside address can be seen on that chain. What is confidential is everything that happens on USD Network itself.
History
Accounts became confidential on 4 November 2026. Transactions sealed before then are served in their public view too, but their details were public until that day, so anyone who copied them then still has them.