DID Webvh Vs DID Web Verifiable Credentials

did:webvh reached version 1.0 in 2026, adding a self-certifying identifier and a signed update history to plain did:web — solving the exact portability problem AuthiChain’s protocol spec sidesteps today by defaulting to did:key instead.

Why AuthiChain

• did:webvh lets a DID move to a new web location without breaking the chain of trust back to its original keys; did:web has no equivalent — change the domain and the identifier is simply gone
• Neither did:web nor did:webvh is what protocol/SPEC.md specifies today: the spec resolves the issuer key from did:key with zero network access, a property did:webvh does not match, since it still requires an HTTPS lookup to resolve
• did:webvh’s verifiable history is a real answer to key rotation, a gap did:key does not solve on its own — a new did:key is a new identifier, with no cryptographic link back to the old one

How it works

Issue a unique identifier per unit, anchor its record on-chain for tamper-evidence, and let anyone verify it with a single scan. Plans start at $49/mo.

FAQ

Does AuthiChain support did:webvh today?

No — the reference verifier resolves did:key only, per protocol/SPEC.md §5 step 2. did:webvh is a candidate for a future issuer-identity option, not something implemented today.

Is did:webvh a replacement for did:web?

It is an extension. did:webvh uses the same DID-to-HTTPS resolution as did:web, then adds a self-certifying identifier and signed update history, addressing did:web’s two open problems — domain lock-in and no proof of what changed on rotation.