What is private by default
- Account balances (behind privacy mode).
- Open positions and unrealized PnL.
- Order-book activity for accounts in Shield Mode.
What stays public
- Block production. Every block, every sealer, every height is public.
- Transaction existence. You can see that a privacy-mode account submitted an order, you cannot see the order details.
- Aggregate market data. Total open interest, traded volume.
- Trades for non-privacy-mode accounts. Shield is opt-in for trades, opt-out for account state.
How it works
- Encrypted orders. Order payload is encrypted before it hits the chain.
- ZK proofs. Each encrypted order is accompanied by a STARK proof that the order is well-formed. The system can match it without decrypting it.
- Stealth addresses. Receiving addresses are derived per-transaction to avoid linkability across trades.
- Viewer Pass. The account holder can selectively reveal data (to a tax tool, an exchange's KYC process, a counterparty) by issuing a viewer credential. The chain itself does not reveal anything without consent.
Account Privacy ON by default
As of chain genesis, every new account ships with Account Privacy enabled. Users opt out, not in. This is why AsterScan's whale tracker and trader leaderboards only surface accounts that have explicitly disabled privacy.
What this means for AsterScan
We cannot show balances or positions for accounts in privacy mode. Period. It is not a feature gap, it is a chain-level guarantee.
What we can show:
- Block production, sealer identity, transaction count.
- Aggregate flow per action type, per market.
- Oracle prices, fee burn, ZK proof verification results.
- The Privacy Adoption Dashboard at /privacy tracks how many accounts use each mode over time.
Shield Mode versus Account Privacy
- Account Privacy. Chain-level, hides your account state.
- Shield Mode. AsterDEX trading product, uses privacy primitives to also hide individual orders during execution.
- You can have Account Privacy ON and trade in Pro Mode (public orders).
- You can have Shield Mode trades on a public account.
Trade-offs
Performance, UX, compliance
- Performance. ZK proof generation adds latency. Aster mitigates this with sub-second proving on the client side.
- UX. Some integrations (third-party PnL trackers, portfolio aggregators) cannot read your account without your Viewer Pass.
- Tax/compliance. You are still responsible for declaring trades. Viewer Pass exists to make this auditable when you need it to be.
Further reading
Last reviewed May 2026. Numbers drift — check the privacy dashboard for current values.
Corrections → @aster_scan