How it works / The quiet path
Same network.
A different story.
A public wallet can reveal balances, payments, and the connections between them.
- Still visible
- Everything: addresses, balances, counterparties, amounts and timing.
- Who is trusted
- Anyone who links the address to you.
Imagine moving into a shared privacy layer, where activity is separated from your public identity.
- Still visible
- The deposit itself — its address, amount and time — is public.
- Who is trusted
- The privacy system's contracts and circuits.
The concept represents sensitive details as sealed notes, readable only with the right access.
- Still visible
- That notes exist and that the pool changed; not who owns which note.
- Who is trusted
- The cryptography and the size of the crowd in the pool.
Explore a private payment without displaying the sender, recipient, or amount in the public view.
- Still visible
- Timing, fees, and metadata seen by relayers and RPC providers.
- Who is trusted
- Relayers or broadcasters that submit transactions.
Share a selected record with an intended recipient. Privacy includes choosing what to disclose.
- Still visible
- Whatever you share — it cannot be un-shared once copied.
- Who is trusted
- The recipient of your records or viewing key.
Illustrative network
Layers & perspectives
Try every
combination.
Tap a layer or use the controls. Masking text here is not blockchain privacy.
Perspective
Anyone with a block explorer. They see what the network publishes — nothing more, nothing less.
Privacy model
Modelled on shielded-pool designs such as RAILGUN on EVM chains.
Choose a layer
- Transfer amountvisible
- Account balancevisible
- Sender addressvisible
- Recipient addressvisible
- Counterparty graphvisible
- App interactionsvisible
- Shared receiptsealed
- Viewer scopesealed
Still visible · no cloaks
- — Balances and amounts
- — Sender and recipient addresses
- — Every relationship and app call
- — Timing of all activity