BitcoinCash/specification
1
Fork 0
Code Issues Pull Requests Releases Activity

Merge branch 'master' of /git/bitcoin-cash-spec

Browse Source
This commit is contained in:
1HXb9KMAtwNJqz4egi6hJx08EQgJajiBTH
2019-12-11 16:14:23 -05:00
parent cc960cf2dc 9e8f64095f
commit f18b156419
2 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
home.md
+1 -1
View File
@@ -79,7 +79,7 @@
- Peer-to-Peer Network - Peer-to-Peer Network
- [Messages](/protocol/network/messages) - [Messages](/protocol/network/messages)
- [Handshake: Version (“version”)](/protocol/network/messages/version) - [Handshake: Version (“version”)](/protocol/network/messages/version)
- verack - [Handshake: Acknowledge ("verack")](/protocol/network/messages/verack)
- ping - ping
- pong - pong
- addr - addr
protocol/network/messages/verack.md
+5
View File
@@ -0,0 +1,5 @@
# Handshake: Acknowledge ("verack")
The `verack` message is sent in reply to a [version](/protocol/network/messages/version) message. Sending a `verack` in response to a `version` message indicates to the remote that its connection and version has been accepted. There is no version negotiation functionality between nodes; therefore if the node does not accept the version supplied by the remote then the node disconnects instead of responding with a `verack`.
This `verack` message consists of only a message header; the command string is "verack".