There’s a lot to this topic. I’m so glad this question has been asked.
I’ve worked with Web5 and those SDKs since its launch. I’m currently building an incubation project with the TBD team called DCX.
I‘ve also worked with Nostr and those SDKs and built hackathon apps that integrated some of the core Nostr features.
After spending time with both, I can say with confidence that the TBD team has a lot of time and put a lot of thought and effort into architecting a cleaner and more scalable.
Nostr does have network, and yes, DIDs can be integrated into Nostr. This is a testament to the flexibility of DIDs and the DID spec. Check out this initial spec with working code examples: https://github.com/bnonni/did-nostr. I’m working on building a live app example of this did:nostr spec to showcase how it works.
TLDR: Nostr keys are a subset of DID keys in terms of functionality. Nostr keys can perform certain functions as good as DIDs such as the basic ability to sign arbitrary data and do authentication. DIDs provide a more scalable solution because they are built with support for other robust features like VCs and DWNs. DIDs are also platform agnostic meaning the second part of the DID uri can be swapped out with any storage solution you want (i.e. did:dht, did:nostr, did:btc, did:ion, did:web).
In the end, these two things are tools. The question becomes: which tool solves my problem more effectively? 🤔 my answer was / is DIDs using Web5.
n0nstr / bryan
npub1nh…5scfr
2024-07-29 14:38:47
in reply to nevent1q…8h95
Author Public Key
npub1nh0klcapjnfnpfkxufu2gv4wzvy72txqskrj2jen0585j8ml7epqp5scfrPublished at
2024-07-29 14:38:47Event JSON
{
"id": "0c5201073f0d4025cbf867cde43e3df2bb653eafbde29a54ff3eb353ea0fb89d",
"pubkey": "9ddf6fe3a194d330a6c6e278a432ae1309e52cc08587254b337d0f491f7ff642",
"created_at": 1722263927,
"kind": 1,
"tags": [
[
"e",
"4e60de682f9630a3961ade80f48412f737870a84c7b4a1b0b077df629584719c",
"",
"root"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"p",
"6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"p",
"82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"
],
[
"p",
"6ad08392d1baa3f6ff7a9409e2ac5e5443587265d8b4a581c6067d88ea301584"
],
[
"r",
"https://github.com/bnonni/did-nostr"
]
],
"content": "There’s a lot to this topic. I’m so glad this question has been asked.\n\nI’ve worked with Web5 and those SDKs since its launch. I’m currently building an incubation project with the TBD team called DCX.\n\nI‘ve also worked with Nostr and those SDKs and built hackathon apps that integrated some of the core Nostr features.\n\nAfter spending time with both, I can say with confidence that the TBD team has a lot of time and put a lot of thought and effort into architecting a cleaner and more scalable.\n\nNostr does have network, and yes, DIDs can be integrated into Nostr. This is a testament to the flexibility of DIDs and the DID spec. Check out this initial spec with working code examples: https://github.com/bnonni/did-nostr. I’m working on building a live app example of this did:nostr spec to showcase how it works. \n\nTLDR: Nostr keys are a subset of DID keys in terms of functionality. Nostr keys can perform certain functions as good as DIDs such as the basic ability to sign arbitrary data and do authentication. DIDs provide a more scalable solution because they are built with support for other robust features like VCs and DWNs. DIDs are also platform agnostic meaning the second part of the DID uri can be swapped out with any storage solution you want (i.e. did:dht, did:nostr, did:btc, did:ion, did:web).\n\nIn the end, these two things are tools. The question becomes: which tool solves my problem more effectively? 🤔 my answer was / is DIDs using Web5.",
"sig": "d29ed4c528e1df186194ec8fc7d172afc548a2b661e2877dbd4ca296fb3cb6fafe6764fd3e1f08b198217a7cbfc63c8f87f10cc779537ca6ec62eecb64399f92"
}