W3C advances DID Resolution to Candidate Recommendation

The World Wide Web Consortium (W3C) has moved the Decentralized Identifier Resolution (DID Resolution) specification to Candidate Recommendation status, marking a key milestone in the development of decentralized identity infrastructure. The standard outlines a process for resolving decentralized identifiers (DIDs) into machine-readable documents that enable cryptographic verification of identity claims without centralized authorities.

What the standard covers

DID Resolution v1 specifies how systems should retrieve a DID document when given a specific DID and optional resolution parameters. The output includes both the document itself—containing public keys and service endpoints—and metadata about the resolution process. This metadata may describe the document's validity period, cryptographic proofs, or other contextual information relevant to the resolution request.

The specification is designed to work across different DID methods, which are implementation-specific schemes for creating, updating, and deactivating DIDs. While the standard does not mandate a particular method, it provides a consistent interface for resolving any compliant DID, regardless of the underlying technology. This interoperability is intended to support use cases such as verifiable credentials, secure authentication, and decentralized access control.

Implementation and feedback timeline

The W3C has opened a feedback period running until 3 September 2026, during which implementers are encouraged to test the specification and submit comments via GitHub issues. The Candidate Recommendation phase is a formal step in the W3C process, indicating that the standard is considered stable enough for real-world testing but may still undergo revisions based on implementation experience.

Potential impact on infrastructure providers

For hosting and cloud infrastructure providers, the advancement of DID Resolution could influence several areas of service delivery. Identity management systems may need to integrate DID resolution capabilities to support customers building decentralized applications or verifiable credential systems. DNS operators and domain registrars might explore DIDs as an alternative or complement to traditional domain-based identifiers, particularly in use cases requiring higher assurance of identity.

The standard could also affect security practices, as DID resolution introduces new cryptographic verification steps that may need to be audited or integrated into existing authentication workflows. Providers offering identity-as-a-service or API security products may see increased demand for DID-compatible features as adoption grows.

What to watch

Industry observers will be monitoring several developments in the coming months. Implementation reports from early adopters will provide insight into the standard's real-world performance and interoperability. Feedback submitted during the comment period may lead to revisions before the specification reaches final Recommendation status.

Additionally, the relationship between DID Resolution and other decentralized identity standards—such as Verifiable Credentials—will be important to watch. As these technologies mature, infrastructure providers may need to assess whether to build native support or partner with specialized identity providers. The timeline for widespread adoption remains uncertain, but the Candidate Recommendation milestone suggests growing momentum behind decentralized identity solutions.