H33-74 on Polygon zkEVM

How H33-74 anchors to Polygon zkEVM

Each anchor is a Polygon zkEVM transaction that commits to a receipt's cryptographic identity (or to a batched commitment covering many receipts). The anchor lives in Polygon zkEVM's canonical ledger and is independently verifiable via any Polygon zkEVM block explorer.

Anchor mechanism on Polygon zkEVM

H33-74 anchors to Polygon zkEVM mainnet via EIP-1559 transactions with the receipt's 32-byte commitment (or batched Merkle root) embedded in calldata. The receipt's identity is committed to L2, and once the L2 batch is proven and posted to Ethereum L1, the anchor inherits L1-grade security.

Chain parameters

What an H33-74 anchor record contains

• The 32-byte commitment from the receipt (or a Merkle root if batched).
• Sufficient on-chain bytes for a third party to verify the commitment matches the receipt.
• A timestamp from the Polygon zkEVM block, providing independent proof that the receipt existed by no later than that block.

What it does not contain: sensitive payload data. The receipt's content lives off-chain. The anchor only commits to its existence and identity.

When Polygon zkEVM is the right anchor

Polygon zkEVM is the right anchor when EVM-compatible tooling is needed, when L1-grade settlement assurance is required but L1 gas costs are not, and when the operator wants the security inheritance of a zk-rollup. Particularly appropriate for RWA and tokenization use cases that need EVM interoperability without paying Ethereum mainnet costs per anchor.

The portability story

A receipt anchored on Polygon zkEVM can also be anchored on Bitcoin, Ethereum, Solana, Polygon zkEVM, Zcash, or any other chain H33-74 supports. The anchors are independent. Adding more anchors does not change the receipt. Removing one anchor (or having one chain become unavailable) does not invalidate the others.

If Polygon zkEVM ever becomes inappropriate for an operator's use case (regulatory, performance, security, cost), the operator adds an anchor on a different chain and continues operating. The historical evidence does not have to migrate, because it was never bound to Polygon zkEVM.

Verifying a Polygon zkEVM anchor

A third-party verifier needs the H33-74 receipt, the Polygon zkEVM anchor transaction (or its hash), and the open-source H33 verifier. From those inputs:

• The verifier checks the three post-quantum signatures over the receipt (ML-DSA-65, FALCON-512, SLH-DSA-128f).
• The verifier checks that the Polygon zkEVM anchor transaction commits to the receipt's identity.
• The verifier reads the Polygon zkEVM block timestamp to establish independent existence-time.

None of those steps depends on H33's infrastructure. The verifier is open-source and the chain is public.

Related