Re: Introducing the Bitcoin Ordinals DID Method

I echo Manu's words, diversity in the DID Method ecosystem is a goal and
benefits the community. The fact that there is a podcast dedicated to
exploring DID methods speaks volumes. Today, I checked, and there are 169
DID methods in the registry.

Exploring and assessing the variety of DID Methods is a terrific learning
process, and highlights the multitude of use cases, trade offs, and

Recently, my favorite DID method topic is "Verification Method Revocation
in Trustless Systems." Those of you familiar with Section 9.8 of the DID
core specification will recognize the section heading.

Attached is a DRAFT deck exploring Verification Method Revocation in
Trustless Systems. Hopefully it will shine a light on the importance of
moving that work forward, and addressing all of the "R" words: recovery,
rotation, revocation, and beyond.

Clare Nelson, CISSP, CIPP/E, AWS CCP
Executive Director
Decentralized Identity Foundation (DIF) <>

On Tue, May 2, 2023 at 8:59 AM Manu Sporny <>

> On Mon, May 1, 2023 at 6:16 PM Brian Richter <> wrote:
> > Yes, we agree Bitcoin as it is currently architected will never support
> billions of users on layer 1 however the bet I'm making is that there will
> be users willing to pay a premium to get their keys and services endpoints
> embedded on layer 1.
> To pile on to the thread, diversity in the DID Method ecosystem is a
> goal. All DID Methods make trade-offs, and as long as the DID Method
> is up-front about the tradeoffs it is making, then that's what
> matters, IMHO.
> While I can't comment on the technical mechanism used in depth, it
> sounds like a perfectly reasonable way to approach the problem if you
> want to use Bitcoin and don't want to depend on a Layer 2 network.
> -- manu
> --
> Manu Sporny -
> Founder/CEO - Digital Bazaar, Inc.

Received on Tuesday, 2 May 2023 15:53:02 UTC