From dbe381b779527e75d6a64f72c7855a9d7664632c Mon Sep 17 00:00:00 2001 From: ArjenStens Date: Thu, 7 Nov 2024 11:50:34 +0000 Subject: [PATCH] wording --- 37.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/37.md b/37.md index ba7f94b4..22d31618 100644 --- a/37.md +++ b/37.md @@ -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.