Security
Privacy limits
| Event | What anyone sees |
|---|---|
| Deposit | Depositor address, asset, exact amount, time. The pending record links the depositor to both output commitments, and so to their asset. |
| Withdrawal | Recipient, asset, exact amount, fee, relayer, time. Its change commitment is asset-labelled. |
| Transfer or claim | Two nullifiers, two commitments, two 113-byte ciphertexts, the root used, and the submitter (the sponsor). No amount, no asset. |
| Refund | Depositor, asset and amount, as public as the deposit it undoes. |
| Payment request | Nothing on Sei. Whoever you send the link to sees your address, and the amount and note if you set them. Paying it is an ordinary private transfer. |
| Payroll | One private transfer per person. Names and amounts are not on Sei. The deposit that funded the balance, and any later withdrawal, stay public. The results file on the sender's phone lists who was paid. |
How the asset claim actually reads
Within private transfers and claims, SEI and USDC notes can't be told apart. Deposit outputs and withdrawal change outputs are asset-labelled, because those transactions name an asset. So a USDC withdrawal hides among every transfer output plus every USDC-labelled leaf, not among SEI-labelled leaves.
Behaviour leaks more than cryptography
- Amounts. 37.12 in, 37.12 out is a link. The app offers round presets.
- Timing. In a quiet pool, a quick round trip is easy to pair.
- Anonymity set. The set is as large as real usage. On testnet it is small, and you should assume it is.
- Old roots reveal an upper bound on when the spent notes were inserted.
- IP addresses. The relayer, the RPC provider and the website host see your IP address.
- Funding account. Every deposit from your funding account is linked to it. Withdrawing back to it links both ends.
- The view key. Anyone with your view key sees all your notes, including unclaimed links you sent. The app does not export it.
Source: apps/web/content/docs/privacy-limits.md