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

changed name

Browse Source
This commit is contained in:
asmogo 2024-12-12 23:10:55 +01:00 committed by GitHub
parent 8631a536b1
commit 81f511d0a8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
74.md
View File

@ -1,7 +1,7 @@
NIP-74 NIP-74
====== ======
Nostr Web Services (NWS) Transmission Control Protocol (TCP)
====== ======
`draft` `optional` `draft` `optional`
@ -68,5 +68,5 @@ will create direct message events for public key `3ef54d9f7eaa3a6fafaea680b1d047
### Basic Control Flow ### Basic Control Flow
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. 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. The client must publish an encrypted event 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. Upon receiving the event, the exit node will process the request according to the specified message type, facilitating communication between the client and the destination.