Confidentiality Model
Darwin's claim, stated exactly: your position is private, and your account is not in the public trade legs. The relay sees your trades. This page says what that means. Public Surface lists, object by object, what an outside observer sees.
The relay design
On testnet, a trade started with a public note sent from your own account, so anyone could read your account id and your trade size. Mainnet removes that:
- You send a private note to Darwin's relay. The chain records that a note exists, not its amount.
- The relay sends every public transaction (DEX orders, the vault's deposit and redeem) from its own account.
- What comes back to you is a private note.
An observer of the vault sees the relay trading, not you.
What is private
| Object | Why |
|---|---|
| Your trade note to the relay | Private P2ID: the chain stores an id and metadata, not the assets |
| Your BLUEDW and USDCx coming back | Private P2ID notes |
| Your balance | In your own account, private if the account is private. Darwin keeps no on-chain list of holders |
| Your trade history | The app keeps it only in your browser. The relay's ledger records every trade to settle it, and shows a trade only to the browser holding its proof |
There is no per-user ledger on-chain, so there is no object whose disclosure would reveal the set of holders.
Who can read a trade's status: per-trade proofs
The relay must answer "is my trade done?" without telling anyone else. Note ids and senders are public on-chain, so knowing a note id proves nothing. Instead, each trade has a view proof:
proof = sha256("darwin.relay.view.v1|" + noteId + "|" + serial of your note)The serial of your private note is generated by your browser and never appears on-chain. Only your browser and the relay's ledger know it. Without the proof, the relay answers only "this note exists, at step N"; amounts, accounts and note files stay closed. Listings by account are closed to the app entirely: the app asks about the trades it holds proofs for, and nothing else.
The consequence, by design: there is no cross-device view. A second device has no proofs and sees nothing. Darwin chose that over adding an account system, because an account system is a list of who traded what.
What the relay sees
The relay is a party to every trade. It knows which account sent what, when, and what it received. It does not publish that. Its alerts and per-trade summary lines redact amounts and accounts (its detailed run logs do not), and its listing endpoints require an operator token that is never deployed to the web app. But "the relay knows" is a trust assumption, not cryptography.
What remains visible on-chain
- That your account sent a note to the relay, and when. A private note's metadata (sender and tag) is public. The amount is not.
- The tag of the note that pays you. The vault's public deposit note carries the recipient digest and tag of your private share note, and a tag is derived from the target account.
- Timing. While Darwin's volume is low, "account X sent a private note to the relay at 12:00, and a public deposit of $40 of coins landed at 12:02" is a strong correlation. It weakens as more trades overlap.
So: private positions, and pseudonymous trades that are hard to read from the chain but not impossible to correlate.
Why that is still worth having
- There is no address-level portfolio view. Nothing in a block explorer shows a Darwin position, yours or anyone's.
- Your account never sends a public trade. An observer of the vault sees the relay, and must correlate timings to guess more.
- The link that would make it identity-level (between an account and a person) is made where funds enter Miden, not inside Darwin.
Closing the remaining gap
- Blinded tags. Share and return notes could use a tag shared by many users, so a tag no longer points at one account.
- Batching. Grouping several users' trades into one deposit removes the one-to-one timing link.
- A private on-ramp. The strongest leak is still where funds enter Miden, outside Darwin.
Threats this model does not address
- The relay operator, or anyone who compromises the relay, can see trades.
- An observer who already knows your account id learns when you trade, but not how much.
- A compromised device: your history and proofs live in the browser.
- Anything Miden itself can see. Darwin inherits Miden's privacy; it adds none below it.