nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-01-08 15:22:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

wording

Browse Source
This commit is contained in:
ArjenStens 2024-11-07 11:50:34 +00:00
parent 70e3cf76d9
commit dbe381b779
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
37.md
View File

@ -30,7 +30,7 @@ There have been NIP proposals that touch the connection between pubkeys and addr
- [NIP-66 - Relay Discovery and Liveness Monitoring](https://github.com/nostr-protocol/nips/pull/230)
#### NIP-97
I believe NIP-97 is very close to solving the issue of this mapping. But it attempts to also include human-readable naming into the solution. I believe that human-readable naming of pubkeys/services is inherently different from mapping a pubkey to an address where a user can access that pubkey's services, which may or may not map to a legacy domain name.
I believe NIP-97 is very close to solving the issue of this mapping. However, it attempts to also include human-readable naming into the solution. I believe that human-readable naming of pubkeys/services is inherently different from mapping a pubkey to an address where a user can access that pubkey's services, which may or may not map to a legacy domain name.
I argue that Nostr introduces a new paradigm of addressing services, and that that creates an opportunity to make services accessible through different networks and protocols at simultaneously.