H33-74 / Comparison

H33-74 vs Microsoft ION

Microsoft ION solves Bitcoin-anchored DID infrastructure. H33-74 solves chain-portable evidence for any operational event, of which DID lifecycle is one specific case.

Microsoft ION is an open implementation of the Sidetree protocol, providing decentralized identifiers (DIDs) anchored to Bitcoin. ION's design center is high-throughput DID operations (create, update, deactivate) batched into Bitcoin transactions with off-chain operations resolution via a content-addressable storage layer.

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

What they share

Both projects use Bitcoin as a notarization surface. Both batch operations off-chain and anchor commitments on-chain. Both target enterprise identity and credential use cases.

Where H33-74 differs

Scope
ION: DID lifecycle (create, update, deactivate, resolve). H33-74: any operational event including identity actions, decisions, approvals, compliance events.
Anchor chain
ION: Bitcoin-only by design. H33-74: any chain, including Bitcoin via Taproot or OP_RETURN.
Signature scheme
ION: secp256k1 ECDSA. H33-74: three-family post-quantum (ML-DSA-65 + FALCON-512 + SLH-DSA-128f).
Primary consumer
ION: DID resolvers, verifiable credential ecosystem. H33-74: auditors, regulators, counterparties verifying operational evidence.
Off-chain storage
ION: content-addressable storage layer (IPFS-style). H33-74: receipt storage is a separate operational concern; the 74-byte proof is sufficient for verification.

When Microsoft ION is the right choice

Microsoft ION is great when the operational concern is decentralized identifier lifecycle in the verifiable credentials ecosystem, when Bitcoin-anchored identity is the design center, and when interoperability with the W3C DID ecosystem is the value.

When H33-74 is the right choice

H33-74 is great when DID lifecycle is one of many operational events needing chain-portable evidence. When post-quantum survivability of identity decisions matters. When the same evidence layer supports identity, compliance, governance, and AI decisions in one consistent format.

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