AIR
Proof Lab
StartEcosystem
Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself
H33-74 on Base

H33-74 on Base

Category · tier-1 reading. This page is one implementation of H33's chain-agnostic integrity thesis. For the concept that spans all 11 supported chains, see Public Integrity Layer.

Anyone recording high-stakes operational evidence needs it to outlive the system that produced it. H33-74 is the primitive that produces and anchors that portable post-quantum evidence — this page shows H33-74 evidence anchored on Base. It expresses the H33-74 primitive for the Base anchor surface; it does not add a new capability.

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

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.

What differs between blockchains are their operational and integration characteristics. The H33-74 primitive and its cryptographic properties remain unchanged. Cost, finality, ecosystem, and settlement model differ between Base and, say, Bitcoin — the 32-byte commitment, the three post-quantum signatures, and the verification steps do not.

Migrating from one blockchain to another changes the anchoring substrate and deployment environment. It does not change the H33-74 primitive, the cryptographic evidence, or the verification model. A receipt first anchored on Base and later anchored on Ethereum or Solana is the same receipt, proven by the same signatures, checked by the same open verifier.

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:

Frequently asked

What is H33-74, and what is Base here?

H33-74 is the portable proof primitive — a 74-byte post-quantum attestation. Base is one interchangeable anchoring substrate that H33-74 evidence can be recorded on. The chain is the transport layer for a notarization; the proof itself is produced and carried by H33-74.

Does anchoring on Base change the proof?

No. Anchoring writes a 32-byte commitment and inherits a Base block timestamp. The cryptographic evidence — three independent post-quantum signatures over the receipt — is unchanged by the choice of chain. H33-74 anchors its evidence to Base; the proof and verification come from H33-74's cryptography, not from Base.

Is the trust from Base or from H33-74?

From H33-74. Base contributes one independent existence-time notarization. Authenticity and unforgeability come from H33-74's signatures and the independent verifier, which behave identically on every chain.

Can I move this proof to another blockchain?

Yes. The same receipt anchors on Bitcoin, Ethereum, Solana, or any supported chain. Migrating from one blockchain to another changes the anchoring substrate and deployment environment. It does not change the H33-74 primitive, the cryptographic evidence, or the verification model.

Does Base's OP Stack settlement give the receipt its finality?

Base contributes a settlement time — L2 soft finality in seconds, L1-inherited hard finality once the OP Stack batch posts to Ethereum. That records when the receipt was anchored on Base. The receipt's validity is established independently by H33-74's post-quantum signatures and exists before and after any single anchor.

When should you choose another chain?

Legitimate reasons exist to prefer a different chain: Bitcoin for the most conservative settlement, Zcash where confidential-transaction ecosystems matter, Hedera or Solana for higher throughput and fixed low fees, Cosmos where an app-specific zone is required. Base is not always the best fit — but whichever chain you choose, the H33-74 primitive stays portable across all of them, so the choice is an operational one, not a change to the proof.

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

Related