From ecd5a349aa7a7fea10b581ecfc1351133cf92093 Mon Sep 17 00:00:00 2001 From: "David A. Harding" Date: Mon, 24 Nov 2014 10:02:21 -0500 Subject: [PATCH] Dev Docs: Correct Connection Establishment Message Order Text said: version/verack/version/verack. Correct order (per code and my own testing) is version/version/verack/verack. --- _includes/guide_p2p_network.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/_includes/guide_p2p_network.md b/_includes/guide_p2p_network.md index 1f65ba84..e5790f41 100644 --- a/_includes/guide_p2p_network.md +++ b/_includes/guide_p2p_network.md @@ -119,7 +119,11 @@ BitcoinJ is generated using the [makeseeds script][]. {% autocrossref %} -Connecting to a peer is done by sending a `version` message, which contains your version number, block, and current time to the remote node. Once the message is received by the remote node, it must respond with a `verack` message, which may be followed by its own `version` message if the node desires to peer. +Connecting to a peer is done by sending a `version` message, which +contains your version number, block, and current time to the remote +node. The remote node responds with its own `version` message. Then both +nodes send a `verack` message to the other node to indicate the +connection has been established. Once connected, the client can send to the remote node `getaddr` and `addr` messages to gather additional peers.