diff --git a/74.md b/74.md
index bf26f75..27414b8 100644
--- a/74.md
+++ b/74.md
@@ -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.