Privacy
Know what is encrypted, what is public, and who can read a private view.
On this page
Encrypted state
Trader order terms, maker bid/ask curves, balances, positions, margin, and account health are encrypted. Arcium computes matching and account updates; the Solana program checks and applies the callbacks.
Public metadata
| Visible on Solana | What it reveals |
|---|---|
| Wallets and accounts | Ownership and links between protocol accounts. |
| Deposits and withdrawals | Token transfer amounts and timing. |
| Quote records | Maker, capacity, expiry, and lifecycle status. |
| Operation receipts | Transaction signatures, timing, and outcome. |
Encryption does not hide wallet activity or prevent inference from predictable quote policies. External Hyperliquid hedges can reveal aggregate maker exposure.
Read permissions
Owners authorize private views. A maker can explicitly grant an operator access to its inventory. Automatic read sessions encrypt results to a device key; the API sponsors the read transaction without receiving that key.
Device storage protects saved snapshots with encryption. An unlocked device and code running on the same origin remain part of that trust boundary.
Recovery trust
Emergency winddown requires three of five configured committee signers. Recovery shares give the committee a path to recover encrypted state if normal computation is unavailable. Privacy therefore depends on committee custody as well as Arcium.