From 05a9ff0094e11afb54df9d45716e11b36ba57d41 Mon Sep 17 00:00:00 2001 From: Jeff Jing Date: Fri, 24 Feb 2023 12:37:48 +0800 Subject: [PATCH] Update and rename nip-did-name.md to NIP-DID-NAME.md --- nip-did-name.md => NIP-DID-NAME.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) rename nip-did-name.md => NIP-DID-NAME.md (95%) diff --git a/nip-did-name.md b/NIP-DID-NAME.md similarity index 95% rename from nip-did-name.md rename to NIP-DID-NAME.md index 5c0eac46..49960981 100644 --- a/nip-did-name.md +++ b/NIP-DID-NAME.md @@ -83,12 +83,20 @@ It can be a single purpose service resolving only one suffixes. It can also be a Here are 2 example of possible Data Providers: -**SDK for JavaScript Client** +**SDK for JavaScript Clients** + +The JavaScript SDK is the most convenient option for JavaScript Client to use. + - [AllDID](https://github.com/dotbitHQ/AllDID) **HTTP API** + +HTTP API service can provide a wider range of applicability. + - [AllDID-API](https://github.com/dotbitHQ/AllDID-api) +> These Data Providers are **not** mandatory. Clients can choose whichever Data Provider the like, as long as it can resolve the DID names they want to support. + ### SubDID SubDID to DID is like a subdomain to a parent domain, indicating some sort of association or belonging between them. Its form is a string separated by a dot, similar to `alice.nostr.bit`. Client can display which DID the SubDID belongs to, or suggest holder of the SubDID to follow other users with the same parent DID.