From 962d800d6ef34cd889d192cc346d5a361ee66626 Mon Sep 17 00:00:00 2001 From: asmogo Date: Sun, 3 Nov 2024 11:08:07 +0100 Subject: [PATCH] renamed nip 74 --- 443.md => 74.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename 443.md => 74.md (96%) diff --git a/443.md b/74.md similarity index 96% rename from 443.md rename to 74.md index d71e053..d7792d6 100644 --- a/443.md +++ b/74.md @@ -1,4 +1,4 @@ -NIP-443 +NIP-74 ====== Nostr Web Services (NWS) @@ -68,7 +68,7 @@ Sending a request to the following domain: will create direct message events for public key `3ef54d9f7eaa3a6fafaea680b1d047248c93408776027317a9535a2056b2ef53` on relay `ws://0.0.0.0:7777`. ### Basic Control Flow -Unlike traditional TCP/IP communications that resolve a domain name to an IP address and establish a direct connection, NIP-443 leverages NOSTR relays as intermediate proxies for TCP communications. +Unlike traditional TCP/IP communications that resolve a domain name to an IP address and establish a direct connection, NIP-74 leverages NOSTR relays as intermediate proxies for TCP communications. The client must send an encrypted direct message to the desired NOSTR public key, following the format outlined in the [Message Format] section. Upon receiving the message, the exit node will process the request according to the specified message type, facilitating communication between the client and the destination.