01 — Methods
Six DID methods. Six resolution paths. Six different trade-offs between decentralization, speed, governance, and stablecoin readiness. The W3C DID Core v1.1 spec (Candidate Recommendation, March 2026) defines the common data model — but the method determines how identifiers are created, resolved, and anchored. This tool maps the landscape.
Each row is a DID method. Each column is a capability that matters for stablecoin compliance. Hover any row to see adopters, resolution path, and spec details.
Select or enter a DID to resolve it. The explorer returns a structurally accurate W3C DID Document with verification methods, service endpoints, and resolution metadata.
Resolve any W3C Decentralized Identifier to inspect its DID Document, verification methods, and service endpoints across six major DID methods.
Supports did:web · did:hedera · did:key · did:ion · did:pkh · did:ethr — W3C DID Core v1.1
Select a DID method above or enter a DID string to explore its W3C-compliant document structure
The DID method is not an implementation detail — it determines your compliance surface area. did:web anchors to DNS, making it natural for enterprises with existing domain infrastructure (Catena Labs uses it for ACK-ID, Notabene uses it for Travel Rule counterparty identification). But DNS is centralized and revocable.
did:hedera anchors to the Hedera Consensus Service, backed by a governing council of 39 institutions including Google, IBM, Boeing, FedEx, and Deutsche Telekom. Wyoming's Frontier Stable Token (FRNT) and Tether's USDT0 both run on Hedera — and its Stablecoin Studio ships with native KYC/AML account flags.
did:key requires no network — pure cryptographic expansion, ideal for ephemeral agent sessions. did:ion anchors to Bitcoin via Sidetree and powers Microsoft Entra Verified ID. did:pkh derives from a blockchain address — zero-friction wallet-native identity.