Privacy

Privacy is architectural, not cosmetic.

The protocol is designed around shielded user transactions, cryptographic proofs and privacy-aware market infrastructure. At the same time, users and operators remain responsible for how they interact with off-chain services and applicable rules. Privacy does not mean absence of risk.

Shielded by default

Values and parties can be protected depending on the flow. The explorer shows when data is shielded by design.

Stealth addresses

Diversified stealth addressing reduces address reuse, making it harder to link multiple receipts from public chain data alone.

Network privacy

Dandelion++ propagation aims to reduce transaction linkability — without promising protection against a global adversary.

Shielded transaction flow

The wallet generates the proof; the Server verifies it without learning private data beyond protocol necessity.

1. User creates transaction
2. Wallet generates proof
3. Server verifies proof
4. Network orders transaction
5. State roots update

sHDEX & nullifiers

The nullifier prevents double-spend; the commitment represents shielded state. sHDEX is the planned native liquid staking, issued to a stealth address with an accruing model and a per-Server cap to reduce concentration.

KYC policy

The protocol does not mandate KYC.

Certification bonds and on-chain reputation are protocol-level trust signals. Individual operators, brokers, gates or platforms may choose their own compliance processes depending on the services they provide and the jurisdictions they serve.

On-chain / shielded / operator-dependent

Some data is public at the protocol level, some is shielded by design, and some depends on each operator's policies. See Legal Disclaimers for details.

Legal disclaimers →
Privacy reduces on-chain data exposure but does not promise absolute anonymity in all off-chain contexts. You are responsible for how you interact with external services.