H33-74 / Comparison

H33-74 vs Sign Protocol

Sign Protocol pioneered on-chain attestation with a unified schema across chains. H33-74 makes the evidence chain-portable instead of multi-chain.

Sign Protocol provides a chain-agnostic-in-marketing-sense attestation primitive. Schemas, attestations, and revocations live on chain, with cross-chain registries letting attestations be referenced from multiple EVM chains. Sign's design center is on-chain composability of attestations across chains.

Different scope. Different design center. H33-74 and Sign Protocol solve adjacent problems. The question is which problem your team is actually trying to solve.

What they share

Both projects acknowledge that single-chain attestation is too narrow. Both produce structured attestations rather than just timestamps. Both have schema concepts for attestation types. Both support multiple chains.

Where H33-74 differs

Attestation location
Sign Protocol: lives on a chain (or referenced across EVM chains). H33-74: off-chain 74-byte proof, chain holds optional notarization pointer.
Chain scope
Sign: EVM ecosystem (plus some specific non-EVM integrations). H33-74: any chain that can hold a 32-byte commitment, including Bitcoin, Solana, Zcash without special wrappers.
Signature scheme
Sign: ECDSA from attester key. H33-74: three-family post-quantum (ML-DSA-65 + FALCON-512 + SLH-DSA-128f).
No-chain operation
Sign: requires at least one chain. H33-74: receipts valid without any chain anchor.
Primary consumer
Sign: smart contracts in the EVM ecosystem (composability). H33-74: auditors, regulators, counterparties consuming evidence that must outlive the operator and the chain.

When Sign Protocol is the right choice

Sign Protocol is great when on-chain composability of attestations across EVM chains is the value being delivered, when attestation consumers are smart contracts, and when the operator is comfortable with pre-quantum signatures for the audit horizon.

When H33-74 is the right choice

H33-74 is great when attestation consumers are auditors and regulators outside the EVM ecosystem. When the receipt needs to survive any single chain's deprecation or compromise. When post-quantum survivability matters. When the audit horizon extends past chain-ecosystem lifetimes.

These are not direct substitutes. They overlap on some dimensions and address different design centers on others. The architectural decision is which property your operation needs to be foundational.

The category H33-74 creates

Chain portability separates evidence from the infrastructure that produced it.

Chain Portability What Gets Preserved

Related comparisons