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

Update 53.md

Browse Source 
I saw that `KIND-10002` is already used by `Relay List Metadata`, so I decided to change to `KIND-10020`
This commit is contained in:
LeandroBitcoiner21 2023-03-24 15:54:39 -03:00 committed by GitHub
parent 97dafc5d6e
commit c599493f0a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
53.md
View File

@ -14,13 +14,13 @@ Nostr Domain System (NDS)
A domain registration system based on nostr where users can create domains associated with their IP addresses and onion, then this data is signed by the user's key and sent to several relays, so that the registrations do not depend on a central server A domain registration system based on nostr where users can create domains associated with their IP addresses and onion, then this data is signed by the user's key and sent to several relays, so that the registrations do not depend on a central server
As IP addresses can change from time to time, domain registration events must be replaceable and therefore are classified as KIND-10002 according to the (NIP-16 Replaceable Events) As IP addresses can change from time to time, domain registration events must be replaceable and therefore are classified as KIND-10020 according to the (NIP-16 Replaceable Events)
## Example: ## Example:
```json ```json
{ {
"kind": 10002, "kind": 10020,
"tags": [ "tags": [
["dr" "Domain1", "ip4:port", "ip6:port", "onion"], ["dr" "Domain1", "ip4:port", "ip6:port", "onion"],
["dr" "Domain2", "ip6:port", "onion"] /* dr = domain register */ ["dr" "Domain2", "ip6:port", "onion"] /* dr = domain register */
@ -37,7 +37,7 @@ There are several ways to avoid confusion due to the same domain being registere
```json ```json
{ {
"kind": 10003, "kind": 10021,
"tags": [ "tags": [
["dro" "domainregistryevent"], ["dro" "domainregistryevent"],
["dro" "domainregistryevent"] /* dro = domain registration organizer */ ["dro" "domainregistryevent"] /* dro = domain registration organizer */
@ -46,7 +46,7 @@ There are several ways to avoid confusion due to the same domain being registere
} }
``` ```
This event should also be replaceable as domain events may need to be changed as stated above, so it is classified as KIND-10003 This event should also be replaceable as domain events may need to be changed as stated above, so it is classified as KIND-10021
It is very important not to depend on a single organizing user, although the domain registration itself is not done by them. It is very important not to depend on a single organizing user, although the domain registration itself is not done by them.