nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update and rename nip-did-name.md to NIP-DID-NAME.md

Browse Source
This commit is contained in:
Jeff Jing 2023-02-24 12:37:48 +08:00 committed by GitHub
parent 309a894425
commit 05a9ff0094
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
nip-did-name.md → NIP-DID-NAME.md
View File

@ -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.