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

removed connectr referrence

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

9
74.md
View File

@ -31,7 +31,6 @@ Every message must have the following format:
"type": "CONNECT",
"data": "GET /hello HTTP/1.1",
"destination": "google.com",
"entryPublicAddress": "<client public IP>"
}
```
The `key` field is used to identify the message and is required. All TCP messages from one stream must have the same key.
@ -40,18 +39,12 @@ 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 `entryPublicAddress` field specifies the public IP address of the client (when the client wants to use the `CONNECTR` message type).
The `type` field specifies the type of message and is required. There are three defined message types within this protocol:
1. `CONNECT`:
- Used to establish an 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).
2. `CONNECTR`:
- Similar to `CONNECT`, but includes a secondary connection from the exit node back to the client.
- The exit node creates a connection to the client using the `entryPublicAddress` provided in the message, allowing bidirectional communication.
3. `DATA`:
- Used for transmitting data to the upstream destination after a connection has been established.
- The `entryPublicAddress` parameter should only be provided when using `CONNECTR` message types.
Messages must be sent using events with `kind:28333`. The content must be encrypted using NIP-44.