Re: [PROPOSAL]: Adopt DID-KR Key Recovery Extension as a CCG Work Item

Manu,

Fully agreed—Christopher's work is exactly the kind of work we need to be
building on, not reinventing. I've already spent time reviewing the
Blockchain Commons stack (SSKR, CSR, ZeWIF, CKM), and it's clear they've
done deep, practical thinking in this space. More importantly, leveraging
what they've already built will save us significant time, effort, and
headache. These aren't just theoretical contributions—they're already
integrated into production wallets, which gives us a huge head start.

We'll prioritize integrating them into the spec, whether through direct
alignment or thorough analysis in the "Alternatives Considered" section
where appropriate. The goal is to stand on the shoulders of existing work,
not duplicate it. We will coordinate closely with them.

Best,

Amir

On Thu, 19 Mar 2026 at 18:23, Manu Sporny <msporny@digitalbazaar.com> wrote:

> On Thu, Mar 19, 2026 at 1:36 AM Christopher Allen
> <ChristopherA@lifewithalacrity.com> wrote:
> > Happy to share more detail on any of these if helpful.
>
> Yes, +1 they're all helpful and are things the DID-KR spec needs to
> analyze and integrate (or have a very good reason why it decided to
> not use one of the mechanisms).
>
> One of the biggest challenges here might be the diversity of key
> recovery strategies and attempting to get down to one per recovery
> category... and attempting to merge as many recovery categories as
> possible to ease implementation burden.
>
> Amir, all of the things Christopher listed should be integrated into
> the spec in some way (at a minimum, in a section that covers
> "Alternatives Considered", though I expect direct integration with the
> spec for some of them is likely given how much work Blockchain Commons
> has put into these features and that they're already integrated with a
> number of blockchain wallets.
>
> -- manu
>
> --
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> https://www.digitalbazaar.com/
>
>

Received on Thursday, 19 March 2026 13:56:29 UTC