H33-74 on Base

Base is one of H33-74's anchor surfaces, not its foundation. The receipt exists before the Base anchor and remains valid if the Base anchor is later supplemented or replaced on another chain. Base provides one independent notarization. H33-74 receipts can carry many.

How H33-74 anchors to Base

H33-74 anchors to Base via EIP-1559 calldata commitments. As an OP Stack chain, Base settlement assurance inherits from Ethereum L1 once the batch posts to L1.

Chain parameters

Chain

Base (chain ID 8453)

Finality

L2 soft finality in seconds; L1-inherited hard finality on Ethereum settlement once the OP Stack batch posts.

Anchor cost

Low cost (typically 10x to 100x cheaper than Ethereum L1) with EVM-compatible calldata commitment.

Explorer

basescan.org

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 Base 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 Base is the right anchor

Base is the right anchor when EVM compatibility is required, when Coinbase ecosystem integration is valuable, when L1-grade settlement assurance through OP Stack is sufficient, and when low cost matters. Especially appropriate for consumer-facing operations and US-regulated entities looking for chain provenance with established corporate operator backing.

The portability story

A receipt anchored on Base 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 Base 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 Base.

Verifying a Base anchor

A third-party verifier needs the H33-74 receipt, the Base 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.
The verifier checks that the Base anchor transaction commits to the receipt's identity.
The verifier reads the Base block timestamp to establish independent existence-time.

See H33-74 on other chains

The same receipts that anchor to Base can anchor to any of the others.

One Receipt. Multiple Chains. H33-74 Overview