mirror of
https://github.com/seigler/dash-docs
synced 2025-07-28 18:26:13 +00:00
parent
69dfa467c6
commit
79e8fb50e7
6 changed files with 76 additions and 51 deletions
|
@ -68,6 +68,7 @@ As of Bitcoin Core 0.11.0, the most recent protocol version is 70002.
|
|||
|
||||
| Version | Initial Release | Major Changes
|
||||
|---------|------------------------------------|--------------
|
||||
| 70012 | Bitcoin Core 0.12.0 <br>(Not released yet) | [BIP130][]: <br>• Added `sendheaders` message
|
||||
| 70002 | Bitcoin Core 0.9.0 <br>(Mar 2014) | • Send multiple `inv` messages in response to a `mempool` message if necessary <br><br>[BIP61][]: <br>• Added `reject` message
|
||||
| 70001 | Bitcoin Core 0.8.0 <br>(Feb 2013) | • Added `notfound` message. <br><br>[BIP37][]: <br>• Added `filterload` message. <br>• Added `filteradd` message. <br>• Added `filterclear` message. <br>• Added `merkleblock` message. <br>• Added relay field to `version` message <br>• Added `MSG_FILTERED_BLOCK` inventory type to `getdata` message.
|
||||
| 60002 | Bitcoin Core 0.7.0 <br>(Sep 2012) | [BIP35][]: <br>• Added `mempool` message. <br>• Extended `getdata` message to allow download of memory pool transactions
|
||||
|
@ -1211,6 +1212,19 @@ header has been omitted.)
|
|||
|
||||
{% endautocrossref %}
|
||||
|
||||
#### SendHeaders
|
||||
{% include helpers/subhead-links.md %}
|
||||
|
||||
{% autocrossref %}
|
||||
|
||||
The `sendheaders` message tells the receiving peer to send new block
|
||||
announcements using a `headers` message rather than an `inv` message.
|
||||
|
||||
There is no payload in a `sendheaders` message. See the [message header
|
||||
section][section message header] for an example of a message without a payload.
|
||||
|
||||
{% endautocrossref %}
|
||||
|
||||
#### VerAck
|
||||
{% include helpers/subhead-links.md %}
|
||||
|
||||
|
|
|
@ -175,6 +175,7 @@ http://opensource.org/licenses/MIT.
|
|||
[ping message]: /en/developer-reference#ping "A P2P network message used to see if the remote host is still connected"
|
||||
[pong message]: /en/developer-reference#pong "A P2P network message used to reply to a P2P network ping message"
|
||||
[reject message]: /en/developer-reference#reject "A P2P network message used to indicate a previously-received message was rejected for some reason"
|
||||
[sendheaders message]: /en/developer-reference#sendheaders "A P2P network message used to request new blocks be announced through headers messages rather than inv messages"
|
||||
[tx message]: /en/developer-reference#tx "A P2P protocol message which sends a single serialized transaction"
|
||||
[verack message]: /en/developer-reference#verack "A P2P network message sent in reply to a version message to confirm a connection has been established"
|
||||
[version message]: /en/developer-reference#version "A P2P network message sent at the begining of a connection to allow protocol version negotiation"
|
||||
|
@ -287,6 +288,7 @@ http://opensource.org/licenses/MIT.
|
|||
[BIP70]: https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki
|
||||
[BIP71]: https://github.com/bitcoin/bips/blob/master/bip-0071.mediawiki
|
||||
[BIP72]: https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki
|
||||
[BIP130]: https://github.com/bitcoin/bips/blob/master/bip-0130.mediawiki
|
||||
[CVE-2012-2459]: https://en.bitcoin.it/wiki/CVEs#CVE-2012-2459
|
||||
[RFC5737]: http://tools.ietf.org/html/rfc5737
|
||||
[secp256k1]: http://www.secg.org/sec2-v2.pdf
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue