Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Dev Docs: Describe Almost All Remaining P2P Network Messages #649
Conversation
saivann
commented on the diff
Nov 21, 2014
| +{% highlight text %} | ||
| +0094102111e2af4d ... Nonce | ||
| +{% endhighlight %} | ||
| + | ||
| +{% endautocrossref %} | ||
| + | ||
| +#### Pong | ||
| + | ||
| +{% autocrossref %} | ||
| + | ||
| +*Added in protocol version 60001 as described by BIP31.* | ||
| + | ||
| +The `pong` message replies to a `ping` message, proving to the pinging | ||
| +node that the ponging node is still alive. Bitcoin Core will, by | ||
| +default, disconnect from any clients which have not responded to a | ||
| +`ping` message within 20 minutes. |
saivann
Contributor
|
|
@harding I just sent you two pull requests to fix minor details. Otherwise texts are very clear and well explained! |
harding
added some commits
Nov 21, 2014
|
@saivann thanks for the review! (I know I said this would probably be the last big pull for a while, but the I think commit f26a57e addresses our discussion about putting changes in the tables; please let me know if I missed something. Thanks again! In the absence of critical feedback, I'll merge this around 02:00 UTC Saturday. |
harding commentedNov 17, 2014
Preview: http://dg0.dtrt.org/en/developer-reference#control-messages
Notes: describing filterload is next on my todo list (it's a bit more complicated than the other messages in this pull). This pull does not describe Bitcoin Core's Tor-compatible features; I don't know much about Tor and learning about it is low on my todo list.