DEFI PRIVACY

Verify Financial Properties Without Seeing the Numbers.

Q: What is DeFi privacy?

DeFi privacy is the expression of the H33 Privacy Layer in which a protocol verifies a financial property such as a balance range, collateral ratio, or portfolio threshold and receives a post-quantum attested boolean without seeing the underlying values. The protocol learns whether the user qualifies, never what the user holds.

Q: Is the mechanism ZK or FHE?

The property is proven with a zero-knowledge proof over encrypted inputs, attested by H33-74. Where a property must be evaluated over data that stays encrypted end to end, fully homomorphic encryption participates, a distinct data-in-use mechanism documented at /fhe/. Both are mechanisms used here; neither owns the concept, which belongs to the Privacy Layer.

Q: When should I not use DeFi privacy?

Do not use it when the need is ongoing computation over data that stays encrypted end to end rather than proving a single property; route to /fhe/. And do not use it expecting a regulatory compliance verdict; for bounded regulatory claims see Compliant Privacy.

Related · tier-1 reading. For the privacy story end-to-end — FHE + STARK proof + portable artifact, see Privacy Layer.

DeFi protocols need to know if a user qualifies -- not what they own. H33 proves balance ranges, collateral ratios, and portfolio thresholds without revealing the underlying values. Post-quantum attested. 32 bytes on-chain.

Schedule Demo Privacy Layer

DEFINITION

What DeFi privacy is.

DeFi privacy is the thematic expression of the Privacy Layer in which a DeFi protocol verifies a financial property — a balance range, a collateral ratio, a portfolio threshold — and receives a post-quantum attested boolean, without ever seeing the underlying values. The protocol learns whether the user qualifies; it never learns what the user holds.

Why this exists: every on-chain balance check today is a broadcast — it exposes the user to MEV bots, front-runners, and surveillance when all the protocol needed was a single true-or-false. DeFi privacy exists to return the boolean and nothing else. The concept is owned by the Privacy Layer; this page is a supporting expression, and any chain named (Solana and others) is a reference environment the evidence anchors to, never a system H33 owns.

Owner, attestation, and mechanism

The property is proven with a zero-knowledge proof (ZK) over encrypted inputs, attested by H33-74 with three post-quantum signature families, and independently verifiable via Verification. Where a property must be evaluated over data that stays encrypted end to end, fully homomorphic encryption (FHE) participates — a distinct data-in-use mechanism, used here, never the owner of this concept.

Owner: Privacy Layer Attestation: H33-74 Mechanism: ZK (+ FHE where needed) Verify independently

THE PROBLEM

Every balance check is a broadcast.

Every on-chain balance check exposes the user to MEV bots, front-runners, and surveillance. A lending protocol that checks collateral reveals the borrower's exact position size. A DEX that verifies trading tier reveals the trader's full portfolio. An insurance contract that checks coverage ratio reveals every holding.

The protocol only needs a boolean -- true or false. Today it gets everything.

THREE ENDPOINTS

One API call. One boolean. Zero exposure.

Each endpoint accepts encrypted financial data, evaluates a property, and returns a post-quantum attested proof that the property holds -- without revealing the data itself.

POST

/api/v1/privacy/defi/balance-range

Balance in range, exact amount hidden.

Lending: prove borrower has sufficient reserves without revealing total holdings
DEX tiers: prove trader qualifies for institutional tier without exposing portfolio size

curl -- balance-range
curl -X POST https://privacy.h33.ai/api/v1/privacy/defi/balance-range \
  -H "Content-Type: application/json" \
  -d '{
    "balance_encrypted": true,
    "min_balance": 100000,
    "max_balance": 10000000,
    "denomination": "USDC"
  }'

POST

/api/v1/privacy/defi/collateral

Ratio meets minimum, values hidden.

Prove collateral-to-debt ratio >= 150% without revealing either value
Liquidation protection without exposing position size or entry price

curl -- collateral
curl -X POST https://privacy.h33.ai/api/v1/privacy/defi/collateral \
  -H "Content-Type: application/json" \
  -d '{
    "collateral_encrypted": true,
    "debt_encrypted": true,
    "min_ratio_percent": 150
  }'

POST

/api/v1/privacy/defi/portfolio-threshold

Portfolio qualifies, holdings hidden.

RWA platforms: prove portfolio meets accreditation tier without revealing positions
Insurance: prove coverage ratio without revealing individual holdings or allocations

curl -- portfolio-threshold
curl -X POST https://privacy.h33.ai/api/v1/privacy/defi/portfolio-threshold \
  -H "Content-Type: application/json" \
  -d '{
    "portfolio_encrypted": true,
    "min_total_value": 1000000,
    "accreditation_tier": "qualified_purchaser"
  }'

EXPOSURE MODEL

What the protocol sees vs. never sees

Protocol Sees

✓ claim_satisfied: true
✓ 32-byte commitment hash
✓ Attestation type (0x63)
✓ PQ signature bundle
✓ Proof timestamp
✓ Solana program ID
✓ Verification status

Protocol Never Sees

× Exact balance amount
× Collateral value
× Debt value
× Portfolio composition
× Individual holdings
× Position sizes
× Wallet address correlation

LIVE API

Real response from privacy.h33.ai

This is the actual response format returned by the DeFi privacy endpoints. The protocol gets a boolean and a commitment. Nothing else.

curl -- balance-range request
curl -X POST https://privacy.h33.ai/api/v1/privacy/defi/balance-range \
  -H "Content-Type: application/json" \
  -d '{
    "balance_encrypted": true,
    "min_balance": 100000,
    "max_balance": 10000000,
    "denomination": "USDC"
  }'

response -- ShieldProofResponse
{
  "claim_satisfied": true,
  "commitment": "a3f8c2d1e9b7054f6a8e3c1d2b9f7054e6a8c3d1f2b9e7054a6f8c3d1e2b9a7",
  "attestation_type": "0x63",
  "proof_size_bytes": 32,
  "chain": "solana-mainnet",
  "solana_program_id": "5eAwAv59YqpnSBMj59KeXhDdLqmn99HBYSjrb6jcLbC5",
  "pq_signatures": {
    "ml_dsa_65": true,
    "falcon_512": true,
    "slh_dsa_128f": true
  },
  "verified": true,
  "timestamp": "2026-05-23T12:00:00Z"
}

The protocol knows the balance is in range. It never learns the amount.

USE CASES

Every DeFi primitive that checks a number

Lending

Collateral Verification

Prove a borrower meets the 150% collateral ratio without revealing position size, entry price, or total collateral value. The liquidation engine gets a boolean, not a balance sheet.

DEX Access

Institutional Tier Qualification

Prove a trader qualifies for institutional-tier fee schedules, deeper liquidity, or block trade access without revealing their portfolio to the exchange or other participants.

Insurance

Coverage Ratio Proof

Insurance protocols can verify that a user's coverage ratio meets requirements for a payout without seeing the underlying portfolio composition or individual position sizes.

RWA Platforms

Accreditation Verification

Real-world asset platforms can verify a user meets qualified purchaser or accredited investor thresholds without the user revealing their complete financial picture.

ARCHITECTURE

Same architecture. No new mental model.

Same 32-byte commitment. Same three-family PQ signing. Same ShieldProofResponse.

DeFi Privacy uses the identical attestation pipeline as every other H33 privacy product. If you have integrated one H33 endpoint, you have integrated all of them. The proof format is the same. The verification path is the same. The Solana program is the same.

32 bytes on-chain ML-DSA-65 + FALCON-512 + SLH-DSA-128f ShieldProofResponse Attestation 0x63 H33-74 proof bundle

BOUNDARY QUESTIONS

Where DeFi privacy begins and ends

1 · Privacy property

Property verified, values hidden

Selective disclosure of a financial property: the protocol receives a boolean that a balance range, collateral ratio, or portfolio threshold holds — and never the amounts.

2 · Context-specific

DeFi primitives that check a number

The properties (collateral ratio, accreditation tier, coverage ratio) are specific to DeFi lending, DEX access, insurance, and RWA. The proof pipeline is shared platform-wide.

3 · Supplied by H33-74

The attestation

H33-74 supplies the post-quantum attestation — three signature families, timestamp, and the 32-byte commitment.

4 · Mechanism

ZK, with FHE where needed

A zero-knowledge proof (ZK) over encrypted inputs; where a property is evaluated over data kept encrypted end to end, FHE participates. FHE is used, never the owner.

5 · What the chain does NOT provide

Anchoring only

The chain (Solana and others) gives permanence and public ordering for the 32-byte commitment — an anchoring surface the evidence anchors to. It provides no privacy and no attestation.

6 · Independent verification

Recompute and check

Verify by recomputing the commitment and checking the three post-quantum signatures — see Verification. No trust in H33 or the protocol required.

7 · Prefer another mechanism when

Encrypted compute is the need

When the requirement is ongoing computation over data that stays encrypted end to end — not proving one property — start at /fhe/.

DECISION GUIDANCE

When to use this, and when not to.

When to use this

✓ A protocol needs a qualify/not-qualify boolean, not the balance
✓ Balance range, collateral ratio, or portfolio threshold checks
✓ You want to stop leaking positions to MEV bots and front-runners
✓ The property proof must be portably attested and verifiable

When NOT to use this

× You need ongoing computation over data kept encrypted — use /fhe/
× A regulator needs a bounded compliance claim — see Compliant Privacy
× You expect this to be an encrypted-compute engine (it proves a property)
× You think the chain provides the privacy (it only anchors)

FAQ

DeFi privacy, in plain terms.

What is DeFi privacy?

DeFi privacy is the expression of the Privacy Layer in which a protocol verifies a financial property — a balance range, collateral ratio, or portfolio threshold — and receives a post-quantum attested boolean without seeing the underlying values. The protocol learns whether the user qualifies, never what the user holds.

Is the mechanism ZK or FHE?

The property is proven with a zero-knowledge proof (ZK) over encrypted inputs, attested by H33-74. Where a property must be evaluated over data that stays encrypted end to end, fully homomorphic encryption participates — a distinct data-in-use mechanism documented at /fhe/. Both are mechanisms used here; neither owns the concept.

When should I NOT use DeFi privacy?

Do not use it when your need is ongoing computation over data that stays encrypted end to end rather than proving a single property — route to /fhe/. And do not use it expecting a regulatory compliance verdict; for bounded regulatory claims see Compliant Privacy.

What does the chain do, and how is the proof verified?

The chain contributes permanence and public ordering for the 32-byte commitment only — an anchoring surface the evidence anchors to, never owns. It provides no privacy or attestation of its own. Verification recomputes the commitment and checks the three post-quantum signatures, independently, per Verification.

Verify Financial Properties Without Seeing the Numbers.

Owner, attestation, and mechanism

Protocol Sees

Protocol Never Sees

Collateral Verification

Institutional Tier Qualification

Coverage Ratio Proof

Accreditation Verification

Same 32-byte commitment. Same three-family PQ signing. Same ShieldProofResponse.

Property verified, values hidden

DeFi primitives that check a number

The attestation

ZK, with FHE where needed

Anchoring only

Recompute and check

Encrypted compute is the need

When to use this

When NOT to use this

Stop broadcasting financial data to verify financial properties.