Agent-008 — Agent GovernanceHATS — Cyber InsuranceH33-74 — Portable ProofPQ Verified — PQ ValidationCryptographic APIs
AIR
The Cryptographic Lifecycle
How It WorksWatch DemoThe MapPatent Portfolio
Architecture
H33-RootAgent-ZeroQ-SignReplayTruth
Cryptographic Services
UpstreamFHE-IQBFVCKKSTFHE
Open Standards
HATSHICSPQ-Verified (New)CRVOISQ-Key
Verification
Conformance SuiteVerification GuaranteesHATS SpecificationArchitectureProtocol Stability
Proof Lab
Cyber Insurance (HATS)BankingGovernmentHealthcareLaw FirmsPayments (WireProof)AI Companies
SDKs & Tools
SDKs HubTypeScript SDKMCP SDKVerifier CLIGitHub
References
DocumentationAPI ReferenceConformance VectorsSchemasBenchmarks
AboutPressPartnersPricingContactLegal
StartEcosystemResearchExplore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself
ETHEREUM PRIVACY

Compliant Privacy for Ethereum.

Related · tier-1 reading. For the integrity anchor that makes this verifiable, see Avalanche Evidence Anchoring.

Tornado Cash failed because it had no compliance layer. H33 provides one. Every token balance, every DeFi position, every swap is visible on-chain. H33 adds post-quantum privacy with per-transaction compliance attestation.

Schedule Demo Privacy Layer Hub
NO PLAINTEXT BALANCE EXPOSURE DETECTEDVerified: --
LIVE ON ETHEREUM MAINNET
Tokenize the World — anchored 2026-05-27
A $50M reference treasury transfer’s full institutional state — every encrypted policy gate, every authority transition, every signature — collapsed to one 32-byte SHA3-256 canonical fact, then anchored to Ethereum mainnet. Not compressed. Fully post-quantum attested.
CONFIRMED · ETHEREUM MAINNET
block 25,184,389 · 2026-05-27 04:49 UTC
Tx Hash:0x38c62e5825…ab0e593f ↗
Calldata:0x5c741f1ce74a759d7b142f08c5f4dae3954f8174708bce1ad7afb7aef996f770
Calldata Size:32 bytes · SHA3-256 · not compressed
SHA3-256 Of:fraud-bundle.json (6,080 bytes)
Cost To Anchor:0.000047 ETH (22,280 gas × 2.108 gwei)
Signer:0xF84E…AA83 ↗
PQ Families:ML-DSA-65 · FALCON-512 · SLH-DSA-128f
The full bundle is independently verifiable. Run the open-source verifier and re-derive this exact 32-byte commitment yourself.
Watch the replay →  ·  Public verifier ↗  ·  Receipt JSON
EXPOSURE COMPARISON
What changes when H33 is in the path

Native Ethereum

  • × Visible token balances
  • × Visible DeFi positions
  • × Visible swap history
  • × Visible lending positions
  • × Visible NFT ownership
  • × Visible ENS resolution
  • × Visible gas usage patterns
  • × Visible MEV vulnerability

H33 Protected

  • ✓ Encrypted transaction workflow
  • ✓ Attested execution proof
  • ✓ Hidden position metadata
  • ✓ Proof-only compliance verification
  • ✓ 32-byte calldata 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: Ethereum Mainnet -- block ... Commitment: 0x... (32 bytes in calldata) 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.
01
Transaction
Encrypted inputs from DeFi protocol
-->
02
STARK Proof
Constraint satisfaction without reveal
-->
03
PQ Signatures
ML-DSA + FALCON + SLH-DSA triple sign
-->
04
Cachee Store
Full proof bundle persisted off-chain
-->
05
EVM Calldata
32-byte commitment on Ethereum L1
32 bytes on-chain. Full proof off-chain. Three PQ families. Zero data revealed.
DISCLOSURE BOUNDARY
What crosses the attestation boundary

NOT REVEALED

  • × Token balances
  • × DeFi positions
  • × Swap history
  • × Lending positions
  • × NFT ownership
  • × ENS identity
  • × Gas patterns
  • × MEV exposure

ONLY REVEALED

  • ✓ Cryptographic validity
  • ✓ Compliance proof
  • ✓ Solvency attestation
  • ✓ Attestation commitment
  • ✓ Verification status
  • ✓ Replay availability
  • ✓ PQ signature bundle
  • ✓ Chain anchor hash
MULTI-CHAIN WITNESSING
Anchored across:
Ethereum
|
Bitcoin
|
Solana
|
Avalanche
Every attestation is witnessed across multiple chains. Cross-chain continuity.

Replay This Attestation

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

Replay ProofView DAGVerify SignaturesHATS Verifier
Built For
Ethereum protocols that need compliant privacy.
DeFi Protocols
Stablecoin Issuers
Institutional Vaults
RWA Tokenization
L2 Rollups
Compliance-First Exchanges
EXPLORE
50 Live Systems 44 ZK Use Cases

Privacy that regulators can verify.

32 bytes on-chain. Post-quantum attestation. The compliance layer Tornado Cash never had.

Schedule Demo

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

Same Primitive · Other Chains
The same 32-byte H33-74 attestation runs across every chain H33 ships on. One primitive, four products, no per-chain verification model.
Ethereum-Privacy · YOU ARE HERE Bitcoin-Privacy Solana-Privacy Polygon-Privacy