Misconception: KERI Is Just Another DID Method

Misconception: "KERI only adds one more DID method to an already crowded DID registry."

KERI can appear in DID form, including did:keri and did:webs, but the protocol is not limited to being a DID method. Its deeper purpose is to provide a trust-spanning identity layer: portable identifiers, verifiable key state, and a way to bridge across ecosystems.

Summary

What the clips cover

• Jonathan Rayback - KERI entering the DID world. DID:Webs is described as KERI's entry into the DID:Webx family, showing how KERI can bridge to W3C DID conventions.
• Jonathan Rayback - many DID methods. The DID ecosystem has many methods, each with its own method-specific rules. KERI's value is not merely adding another name to that list.
• Jonathan Rayback - did:keri. DID:KERI exists and is simple in form: the DID method prefix plus the AID. That mapping exposes KERI identifiers to DID tooling.
• Thomas Mayfield - portable trust and AIDs. KERI's core identity object is the AID, a portable cryptographic identifier whose authority comes from its own keys and events.

Why it matters

If KERI is treated only as "another DID method," its main architectural contribution gets missed. The Medium guide frames KERI as an identity overlay for the internet, while the LF Decentralized Trust article describes KERI as part of a trust-spanning layer that lets telecom, healthcare, government, and finance compose without one platform controlling them all.

Sources

• The Hitchhiker's Guide to KERI, Part 2
• The Hitchhiker's Guide to KERI, Part 3
• A Day in your Life with KERI