Privacy and disclosure
The proposed confidentiality policy defines who can access account data and what public observers may still infer.
Private position information#
The intended private state includes order intent, direction, size, entry, collateral balance, liquidation level, order history and funding charges. It must remain confidential across contract data, events, account APIs and operational logs.
A private interface over a public HyperCore account wouldn't protect the underlying position records. SubLiquid's position ledger requires its own confidential execution and settlement design.
The visibility boundary#
| Information | Intended access |
|---|---|
| Orders and positions | Trader and authorized execution/risk services |
| Withdrawal authority | Account owner |
| Custody and aggregate reserves | Public or independently attestable |
| Deposits and withdrawals | Public boundary transactions unless a qualified confidential route applies |
| External hedges | Public venue exposure, without a customer identity attached |
Disclosed operator access#
Privacy from public observers doesn't mean operator-blind anonymity. Authorized risk access requires defined permissions, audit trails, retention rules and an incident-disclosure policy. Users must know these boundaries before depositing.
What observers may infer#
Amounts, addresses and timing at deposit or withdrawal can correlate activity. Small aggregate updates and one-for-one hedges may reveal a trader's behavior. Netting and encryption reduce some exposure; neither guarantees anonymity.