mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-22 00:25:50 -05:00
changed name
This commit is contained in:
parent
8631a536b1
commit
81f511d0a8
6
74.md
6
74.md
|
@ -1,7 +1,7 @@
|
|||
NIP-74
|
||||
======
|
||||
|
||||
Nostr Web Services (NWS)
|
||||
Transmission Control Protocol (TCP)
|
||||
======
|
||||
|
||||
`draft` `optional`
|
||||
|
@ -68,5 +68,5 @@ will create direct message events for public key `3ef54d9f7eaa3a6fafaea680b1d047
|
|||
### 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.
|
||||
|
||||
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.
|
||||
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 event, the exit node will process the request according to the specified message type, facilitating communication between the client and the destination.
|
||||
|
|
Loading…
Reference in New Issue
Block a user