Explanation Layer
How It WorksWatch DemoThe MapWhy It Changes EverythingPatents Portfolio
The Subsystems
H33-74 (Substrate)UpstreamH33-TRUTHReplay
Open Programs
PQ Conversion 1,000 (Free)
Core Infrastructure
H33-74UpstreamH33-TRUTHReplay EngineQ-SignFHE-IQ
AI & Governance
Agent-ZeroAI ComplianceGovernance ReplayContinuous AI GovernanceAgent AttestationAgent Replay
Data & Encryption
H33-VaultH33-ShieldH33-ShareEncrypted SearchStorage EncryptionMedVaultQuantumVaultVaultKey
Tokenization & Finance
TokenizationWire ProofDigital Asset GovernanceFraudShieldCyber Claim Verification
Post-Quantum Systems
H33-128 (BFV)H33-256 (L5)CKKSTFHETFHE BootstrapH33-CompileFHE OverviewH33-3-KeyArchiveSignH33-GatewayH33-MPCPQC ArchitectureDeviceProof
Identity & ZK
BiometricsZK-KYCZK-VerifyZK-PhishZK-TrustlessZKP-AIRZK-Attestation
Healthcare & Industry
H33-HealthOperational IntegrityContinuous AttestationContinuous Control Monitoring
Continuous Monitoring
Continuous Control MonitoringContinuous AttestationOperational Integrity
AI Governance
AI Agent GovernanceContinuous AI GovernanceAgent AttestationAgent Replay
Privacy & Chains
Privacy LayerZK-AttestationChain-Agnostic PrivacyDigital Asset Governance
Infrastructure
Governance ReplayPost-Quantum ConversionAttestation APIPost-Quantum APICyber Claim Verification
Open Standards
HATSHICSCRVOISQ-Key
Verification
Conformance SuiteVerification GuaranteesHATS SpecificationArchitectureProtocol Stability
Validation
Adversarial ValidationDeterministic ReplayConformance VectorsAgent Benchmarks
Verification
Public VerifierSession Replay ExplorerGovernance ReplayIndependent VerificationVerify The Story
Live Demos
Tokenization Identity (New)Live Systems (52)Live API TestLive AuthenticationEncrypted ComputeAI Classification
Performance
BenchmarksUse Cases (44)H33 vs SEALWhite PaperHICS Code Scoring
Cyber Insurance (HATS)BankingGovernmentHealthcareLaw FirmsPayments (WireProof)AI Companies
SDKs & Tools
SDKs HubTypeScript SDKMCP SDKVerifier CLIGitHub
References
DocumentationAPI ReferenceConformance VectorsSchemasBenchmarks
AboutPressPartnersPricingContactLegal
Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself
POLYGON‑PRIVACY

The same 74 bytes, now on Polygon zkEVM.

Solana-Privacy proved compliance to the regulator and privacy to the user on Solana devnet today. Polygon-Privacy brings the same H33-74 attestation to EVM-native rails — DeFi, RWA, and traditional-finance settlement.

Schedule Demo See Solana-Privacy (Live)
POLYGON zkEVM RPC · LIVE
Polygon zkEVM mainnet (chain ID 1101) RPC connectivity is live on this page — current block … (updates in real time via WebSocket). Public anchor endpoint ships next per H33_POLYGON_INTEGRATION. Solana-Privacy is live on devnet today.
DEPLOYMENT STATUS
Polygon zkEVM — rollout status
POLYGON zkEVM RPC LIVE — public anchor endpoint next
Updated …
Polygon zkEVM connectivityCONNECTING…
Polygon zkEVM block…
WebSocket subscriptionconnecting…
Target chainPolygon zkEVM (mainnet 1101 · cardona 2442)
First milestonePath 1 anchor — cardona testnet
ETA Path 11–2 weeks
ETA Path 24–8 weeks (on-chain STARK verifier)
Contract addressTBD — coming Q3 2026
Receipt size74 bytes (unchanged)
On-chain footprint32 bytes (calldata commitment)
PQ signaturesML-DSA-65 + FALCON-512 + SLH-DSA-128f
ReferenceSolana-Privacy — live on devnet ↗
EXPOSURE COMPARISON
What changes when H33 is in the path on Polygon zkEVM

Native Polygon zkEVM

  • × Visible wallet balances
  • × Visible ERC-20 holdings
  • × Visible DeFi positions
  • × Visible RWA token ownership
  • × Visible bridge flows from Ethereum
  • × Visible counterparties
  • × Visible contract interactions
  • × Visible settlement history

H33 Protected

  • ✓ Encrypted position workflow
  • ✓ Attested execution proof
  • ✓ Hidden wallet metadata
  • ✓ Proof-only balance verification
  • ✓ 32-byte calldata commitment
  • ✓ Independent STARK verification
  • ✓ Post-quantum attestation
  • ✓ Replay-grade evidence
ATTESTATION RECEIPT
What a verified attestation will look like
Identical to Solana-Privacy receipt structure. Same 74-byte H33-74 bundle. Anchor target swaps from Solana PDA to Polygon zkEVM calldata.
h33-74 attestation receipt — polygon zkevm (preview)
H33-74 ATTESTATION RECEIPT Receipt ID: h74_attest_polygon_zkevm_... DAG Root: 0x... (depth: 4, nodes: 12) Proof Hash: 0x... (STARK, 128-bit PQ security) Replay Ref: replay://h33.ai/r/... Chain Anchor: Polygon zkEVM — cardona testnet — block [pending] 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 →
TRY IT
Anchor a 74-byte H33-74 receipt on Polygon zkEVM mainnet
PREVIEW · POLYGON zkEVM MAINNET STREAM IS LIVE · PUBLIC ANCHOR ROUTE PENDING

Type a string. (Anchor submission currently gated.)

The same 74-byte H33-74 bundle that ships on Bitcoin and Solana — signed with the three-family PQ stack (ML-DSA-65 + FALCON-512 + SLH-DSA-128f), pinned to Polygon zkEVM mainnet as 32-byte calldata, and re-verifiable locally via a 47 KB WASM module. The Polygon zkEVM mainnet stream above is live now; the one-click anchor submission below is being rate-limited before public release.

Anchor submission currently requires an authenticated H33 API key. Public one-click anchoring is being rate-limited before release. Email support@h33.ai for an API key, or watch the mainnet block stream below until the public anchor route ships.

Max 256 chars · public rate limit + IP cap shipping with the public anchor route · submission today returns 401 unless an authenticated API key is attached
·Minting H33-74…
·Signing three-family PQ bundle…
·Anchoring to Polygon zkEVM mainnet…
·Waiting for L2 finality…
·Verifying locally (WASM)…
Anchored on Polygon zkEVM mainnet
VERIFIED LOCALLY
Transaction hash
—
Block number
—
H33-74 receipt (74 bytes)
—
Signing message (32 bytes on-chain)
—
H33-74 Whitepaper Independent Verifier
CHAIN STATUS · connecting…
Polygon zkEVM mainnet block ——— · — · 0 updates
ATTESTATION PIPELINE
Five stages. 32 bytes on-chain.
01
User Data
Encrypted inputs from wallet or 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
zkEVM Calldata
32-byte commitment on Polygon zkEVM
32 bytes on-chain. Full proof off-chain. Three PQ families. Zero data revealed. 74 bytes total — same primitive that ships on Solana, Bitcoin, and Ethereum.
TECHNICAL SPECS
Polygon zkEVM target parameters
Chain (mainnet)
Polygon zkEVM
chain ID 1101 · zkEVM rollup secured by Ethereum
Chain (testnet)
Cardona
chain ID 2442 · first deployment target
Block time
~2 seconds
L2 block cadence; sequencer-driven
Finality
~30–60 minutes
Ethereum-anchored zk-proof finality
Anchor cost
~$0.001 / anchor
Calldata commitment; 100×+ cheaper than Ethereum mainnet
Receipt
74 bytes
Identical H33-74 bundle — unchanged across all chains
On-chain footprint
32 bytes
signing_message as calldata (Path 1) or contract storage (Path 2)
PQ signature stack
3 families
ML-DSA-65 + FALCON-512 + SLH-DSA-SHA2-128f-simple
Proof system
ZK-STARK
Lookup STARK + AIR STARK; no trusted setup
On-chain verifier
Solidity (Path 2)
Audit-gated; pre-mainnet review by STARK-fluent firm
DISCLOSURE BOUNDARY
What crosses the attestation boundary

NOT REVEALED

  • × Wallet balance
  • × ERC-20 holdings
  • × DeFi positions
  • × Bridge flows
  • × Counterparty identity
  • × Contract interactions
  • × RWA ownership
  • × Settlement history

ONLY REVEALED

  • ✓ Cryptographic validity
  • ✓ Compliance proof
  • ✓ Balance sufficiency
  • ✓ Attestation commitment
  • ✓ Verification status
  • ✓ Replay availability
  • ✓ PQ signature bundle
  • ✓ Chain anchor hash
MULTI-CHAIN WITNESSING
Same H33-74 receipt, anchored across:
Bitcoin
|
Solana (devnet)
|
Ethereum
|
Polygon zkEVM (scoping)
Same 74-byte primitive across every chain. Cross-chain continuity without rewriting the attestation format.

Tornado Cash proved privacy without compliance becomes a regulatory dead end.

Polygon-Privacy proves privacy to the user while proving compliance to the regulator — post-quantum signed, replayable offline, and portable across Bitcoin, Solana, and Polygon zkEVM.

That’s the operational primitive institutional AI and RWA systems are missing.

Introducing H33-74. 74 bytes. Any computation. Post-quantum attested. Forever.
Anchored on Bitcoin, Solana, and now Polygon zkEVM.

Replay any attestation. Verify independently.

Every H33-74 receipt is reconstructible from its commitment. Inspect lineage. Inspect proof. Inspect DAG. Verify signatures.

Replay Proof View DAG Verify Signatures HATS Verifier
Built For
Institutions building on Polygon zkEVM at scale.
DeFi Protocols
RWA Tokenization
Stablecoin Issuers
Institutional Desks
TradFi Settlement
Compliance Teams
EXPLORE
50 Live Systems 44 ZK Use Cases Solana-Privacy (Live)

Same 74 bytes. EVM-native rails. Coming to Polygon zkEVM.

Compliance to the regulator. Privacy to the user. Post-quantum attestation that survives the day a quantum computer cracks ECDSA.

Schedule Demo

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

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 Bitcoin-Privacy Solana-Privacy Polygon-Privacy · YOU ARE HERE