What is Hyperliquid privacy?

Hyperliquid privacy is a chain-specific expression of the H33 Privacy Layer. It protects the privacy of trading evidence, trader identity, and position interaction on Hyperliquid while still allowing compliance and margin sufficiency to be verified. Evidence is produced by H33-74 and anchored to Hyperliquid L1 as a 32-byte commitment; Hyperliquid is a reference environment, not the owner of the privacy property.

Does H33 use ZK or FHE for Hyperliquid privacy?

It uses zero-knowledge (STARK) proofs together with data minimization and selective disclosure, plus H33-74 post-quantum attestation. It does not use FHE. If you need computation over data that stays encrypted, use H33 FHE at /fhe/ instead.

What does Hyperliquid provide versus H33?

Hyperliquid provides a public settlement environment the commitment anchors to; it provides no position privacy or attestation. The privacy property, the three-family post-quantum signatures, and portable independently-verifiable evidence are supplied by H33-74 and the Privacy Layer.

When should I use a different chain or mechanism?

Use another chain's privacy page (Solana, Optimism, Polygon, Zcash) if your activity is not on Hyperliquid, and use FHE when you must compute over still-encrypted data rather than prove facts about trades.

Hyperliquid Privacy: Institutional Perpetual Trading

LIVE ATTESTATION

Hyperliquid L1 -- current anchor status

Connecting to Hyperliquid L1...

EXPOSURE COMPARISON

What changes when H33 is in the path

Native Hyperliquid

× Visible positions and sizes
× Visible liquidation levels
× Visible PnL (realized + unrealized)
× Visible strategy timing patterns
× Visible wallet clustering
× Visible counterparty graph
× Front-runnable order flow
× Copyable alpha

H33 Protected

✓ Encrypted position workflow
✓ Attested execution proof
✓ Hidden position metadata
✓ Proof-only margin verification
✓ 32-byte chain commitment
✓ Independent verification
✓ Post-quantum attestation
✓ Replay-grade evidence

ATTESTATION RECEIPT

What a verified attestation looks like

                
                h33-74 attestation receipt
            
H33-74 ATTESTATION RECEIPT

Receipt ID:     h74_attest_...
DAG Root:       0x... (depth: 4, nodes: 12)
Proof Hash:     0x... (STARK, 128-bit PQ security)
Replay Ref:     replay://h33.ai/r/...
Chain Anchor:   Hyperliquid L1 -- block ...
Commitment:     0x... (32 bytes on-chain)

SIGNATURES:
  ML-DSA-65:    VALID (3,309 bytes -- MLWE lattice)
  FALCON-512:   VALID (666 bytes -- NTRU lattice)
  SLH-DSA-128f: VALID (17,088 bytes -- hash-based)

VERIFICATION:   ALL CHECKS PASSED (20/20)
HATS LEVEL:     Level 1 Conformance
CACHEE KEY:     cachee://h33.ai/c/...

Replay This Attestation -->    Verify Independently -->

ATTESTATION PIPELINE

Five stages. 32 bytes on-chain.

Position Data

Encrypted inputs from trading system

-->

STARK Proof

Constraint satisfaction without reveal

-->

PQ Signatures

ML-DSA + FALCON + SLH-DSA triple sign

-->

Cachee Store

Full proof bundle persisted off-chain

-->

HL Anchor

32-byte commitment on Hyperliquid L1

            32 bytes on-chain. Full proof off-chain. Three PQ families. Zero positions revealed.
        

DISCLOSURE BOUNDARY

What crosses the attestation boundary

NOT REVEALED

× Position size
× Liquidation price
× Entry price
× Strategy logic
× Counterparty identity
× Wallet cluster
× PnL history
× Order flow

ONLY REVEALED

✓ Cryptographic validity
✓ Compliance proof
✓ Margin sufficiency
✓ Attestation commitment
✓ Verification status
✓ Replay availability
✓ PQ signature bundle
✓ Chain anchor hash

MULTI-CHAIN WITNESSING

Anchored across:

Hyperliquid

Bitcoin

Ethereum

Solana

Every attestation is witnessed across multiple chains. Cross-chain continuity.

Replay This Attestation

Inspect lineage. Inspect proof. Inspect DAG. Verify signatures.

Replay Proof View DAG Verify Signatures HATS Verifier

Built For

Institutions that trade perpetuals at scale.

Institutional Traders

Market Makers

Prop Trading Desks

Fund Managers

OTC Desks

Compliance Teams

WHAT THIS IS

Hyperliquid privacy, defined

Hyperliquid privacy is a chain-specific expression of the H33 Privacy Layer — it protects the privacy of trading evidence, trader identity, and position interaction on Hyperliquid while still letting a counterparty, venue, or regulator verify compliance and margin sufficiency. The evidence is produced by H33-74 and anchored to Hyperliquid L1 as a 32-byte commitment; Hyperliquid is a reference environment the proof records against, never the owner or producer of the privacy property.

Why this exists: every position, size, liquidation level, and PnL on Hyperliquid is public by default, so front-runners and copy-traders can read an institution's book in real time. This page exists to make trading facts provable without being visible — keeping the strategy private while the obligations stay verifiable. The mechanism here is zero-knowledge (STARK) proof plus selective disclosure and H33-74 attestation. It is distinct from encrypted compute (FHE), which keeps data encrypted while it is being processed.

When to use this

Use this when you trade perpetuals on Hyperliquid and must prove margin, compliance, or performance without revealing positions.
Use this when the evidence must anchor specifically to Hyperliquid L1.
Use this when a counterparty needs to re-verify your proof independently.

When NOT to use this

Do not use this when your activity lives on another chain — use Solana, Optimism, or Polygon privacy instead.
Do not use this when you need computation over still-encrypted data — use FHE instead.
Do not use this to obscure obligations from a regulator — it proves compliance, it does not hide it.

BOUNDARY QUESTIONS

1. What privacy property is provided?

Position sizes, entry and liquidation prices, PnL, counterparties, and strategy timing stay hidden, while cryptographic validity, compliance, and margin sufficiency remain provable. It is bounded confidentiality of trading evidence, not anonymity.

2. What is specific to Hyperliquid?

The reference environment: the commitment anchors to Hyperliquid L1, and the relevant exposure is public perpetual-futures order flow. The primitive itself is unchanged from every other chain.

3. What remains supplied by H33-74?

The 74-byte post-quantum attestation, three-family PQ signature bundle, replay reference, and portability of the evidence across chains are all supplied by H33-74. Hyperliquid supplies none of it.

4. Is the mechanism ZK, FHE, minimization, selective disclosure, or a combination?

A combination of zero-knowledge (STARK) proof, data minimization (32 bytes on-chain), and selective disclosure. It does not use FHE — for encrypted compute see /fhe/.

5. What does Hyperliquid itself NOT provide?

Hyperliquid provides no position privacy, no selective-disclosure proof, no post-quantum attestation, and no portable independently-verifiable evidence. Native trading data is fully public.

6. How is the resulting evidence independently verified?

Through H33 Verification — replay the STARK proof, re-check the three PQ signatures, and confirm the on-chain commitment with the open-source verifier. No trust in H33 or Hyperliquid is required.

7. When should another chain or privacy mechanism be preferred?

Prefer another chain page when the activity is not on Hyperliquid, and prefer FHE when the requirement is computing over data that must stay encrypted rather than proving facts about it.

Stop broadcasting your positions to the market.

32 bytes on-chain. Post-quantum attestation. Position privacy for the largest on-chain perpetuals exchange.

Schedule Demo

H33.ai, Inc. · Patents Pending · HATS Standard · Privacy Layer · H33-74