H33-74 on Hedera

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

How H33-74 anchors to Hedera

H33-74 anchors to Hedera via the Hedera Consensus Service (HCS), which is purpose-built for timestamped message ordering, and as an alternative via Hedera Smart Contract Service (HSCS) calldata. HCS is the canonical choice for commitment notarization given its fee economics and ordering guarantees.

Chain parameters

Chain

Hedera (chain ID 295)

Finality

Instant finality via aBFT hashgraph consensus; finality at consensus typically within 3 to 5 seconds.

Anchor cost

Predictable USD-denominated fees (typically a fraction of a cent per anchor) thanks to Hedera's fixed-fee pricing model.

Explorer

hashscan.io

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

Hedera is the right anchor when enterprise-grade governance (Hedera Council membership) is required, when predictable USD-denominated fees matter for budgeting, when high-throughput consensus-grade ordering is the value being delivered, and when HCS's purpose-built timestamping fits the operational pattern. Particularly appropriate for enterprises that already have a Hedera Council relationship.

The portability story

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

Verifying a Hedera anchor

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

See H33-74 on other chains

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

One Receipt. Multiple Chains. H33-74 Overview