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

fix spacing

Browse Source
This commit is contained in:
asmogo 2024-12-12 22:46:54 +01:00 committed by GitHub
parent 82f024745f
commit 2f77598078
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
74.md
View File

@ -33,6 +33,7 @@ Every message must have the following format:
"destination": "google.com", "destination": "google.com",
} }
``` ```
The `key` field is used to identify the message and is required. All TCP messages from one stream must have the same key. The `key` field is used to identify the message and is required. All TCP messages from one stream must have the same key.
The `data` field contains the data to be transmitted to the destination. The `data` field contains the data to be transmitted to the destination.
@ -40,10 +41,11 @@ The `data` field contains the data to be transmitted to the destination.
The `destination` field specifies the destination of the TCP connection (if the exit node wants to establish a connection to a remote server). The `destination` field specifies the destination of the TCP connection (if the exit node wants to establish a connection to a remote server).
The `type` field specifies the type of message and is required. There are three defined message types within this protocol: The `type` field specifies the type of message and is required. There are three defined message types within this protocol:
1. `CONNECT`: 1. `CONNECT`:
- Used to establish the initial TCP connection. - Used to establish the initial TCP connection.
- The exit node receives this message to initiate a TCP connection with the upstream target (the destination). - The exit node receives this message to initiate a TCP connection with the upstream target (the destination).
3. `DATA`: 2. `DATA`:
- Used for transmitting data to the upstream destination after a connection has been established. - Used for transmitting data to the upstream destination after a connection has been established.
Messages must be sent using events with `kind:28333`. The content must be encrypted using NIP-44. Messages must be sent using events with `kind:28333`. The content must be encrypted using NIP-44.