- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Fri, 20 Feb 2026 09:38:34 -0500
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: W3C Credentials CG <public-credentials@w3.org>
On Fri, Feb 20, 2026 at 5:02 AM Melvin Carvalho <melvincarvalho@gmail.com> wrote: > For more detail, here’s a longer piece on how did:nostr fits within this broader landscape, for those less familiar with it: > > https://melvin.me/public/articles/did-nostr.html FWIW, I found that web page really compelling Melvin. I suggest that those interested in decentralized DID Methods read it because if we were to just delete "nostr" from the entire page, I think it outlines a number of the ideal set of features we're looking for in a fully decentralized DID Method. I find myself internally conflicted about "How many DID Methods are enough?". On the one hand, "at least three -- generate from public key, Web/DNS-based, and fully decentralized"... and on the other hand, there are MANY different types of vehicles in the world, and even more brands that specialize in aspects of each type of vehicle. Perhaps there should be as many different types of DID Methods in time? Well, maybe not as many because there is only so much to differentiate DID Methods from each other... but certainly more than three, or possibly ten. Is twenty five too many? Fifty? More specifically, Melvin, I'm wondering if the "alsoKnownAs" equivalence could work in reverse. Where we add something to did:key, such as: did:key:...?aka=nostr, which would auto-generate the nostr-equivalent key. IOW, it would hint that you could do a nostr lookup that might work via a did:key? -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Friday, 20 February 2026 14:39:15 UTC