- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Thu, 19 Mar 2026 06:56:10 +0100
- To: Amir Hameed <amsaalegal@gmail.com>
- Cc: W3C Credentials CG <public-credentials@w3.org>
- Message-ID: <CAKaEYhJ0JWZMmEC6mU_EVU-CpAcLcbg4P_WOneBNcJ5=+1dC+Q@mail.gmail.com>
čt 12. 3. 2026 v 8:52 odesílatel Amir Hameed <amsaalegal@gmail.com> napsal: > Dear CCG Members, > > Two weeks ago I shared the draft specification for *DID-KR: Key Recovery > Extension for Decentralized Identifiers* for community review and > feedback. > > Thank you to everyone who took the time to review the proposal and > contribute to the discussion. The feedback from members of the group has > been very helpful in refining the direction of the specification and > validating the problem space around decentralized identity key recovery. > > The DID-KR proposal introduces a recovery verification relationship for > DID Documents and specifies multiple recovery mechanisms, including: > > • Social guardian-based recovery using verifiable secret sharing and > zero-knowledge proofs > • Deterministic seed-based recovery mechanisms > • MPC-mediated recovery suitable for enterprise or infrastructure > deployments > > The goal of the specification is to provide a standardized and > interoperable approach to recovering control of decentralized identifiers > when private keys are lost, while maintaining the self-sovereign principles > of decentralized identity. > > The draft specification and issue tracker are currently hosted at Issues > · sirraya-labs/did-kr <https://github.com/sirraya-labs/did-kr> and are > open for community participation and contributions. > > Specification repository: > https://github.com/sirraya-labs/did-kr > > Given the discussion and the interest expressed in exploring > implementations, I would like to formally propose that the *DID-KR Key > Recovery Extension* be adopted as a work item of the Credentials > Community Group. > > I would be happy to serve as editor for the specification and coordinate > with members of the community interested in reviewing, improving, or > experimenting with implementations of the proposal. > > Implementers and contributors interested in exploring prototype > implementations or interoperability considerations are very welcome to > participate. > > Thank you again to the community for the constructive feedback and > discussion. > Key recovery remains an open problem in the Nostr ecosystem. Users who lose their nsec lose their entire social identity: followers, reputation, and verification relationships, with no recovery path. The did:nostr community is very interested in this use case. It would be valuable for the specification to remain mechanism-agnostic and practical enough to serve deployed networks with real users, alongside enterprise and MPC-based approaches. We've seen multiple competing proposals for key migration in Nostr, none of which have converged. A DID-layer standard could help break this deadlock. We support adoption of DID-KR as a CCG work item and would welcome contributing implementation experience from the Nostr ecosystem. Best regards, > > Amir Hameed Mir >
Received on Thursday, 19 March 2026 05:56:26 UTC