Content - P2P - mnget message update

- Related to #41
This commit is contained in:
thephez 2018-06-28 13:40:39 -04:00
parent 44c55257a8
commit 57abe09178
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099

View file

@ -2584,6 +2584,16 @@ The `mnget` message requests masternode payment sync. The response to an
`mnget` message is `mnw` message inventories. Masternodes ignore this request if
they are not fully synced.
{% highlight text %}
Note: Dash Core limits how frequently a masternode payment sync can be
requested. Frequent requests will result in the node being banned.
{% endhighlight %}
There is no payload in a `mnget` message. See the [message header
section][section message header] for an example of a message without a payload.
![Warning icon](/img/icons/icon_warning.svg) **The following information is provided for historical reference only.**
In protocol versions <=70208, the `mnget` message has a payload consisting of an
integer value requesting a specific number of payment votes. In protocol versions
>70208, the `mnget` message has no payload.
@ -2592,11 +2602,6 @@ integer value requesting a specific number of payment votes. In protocol version
| ---------- | ----------- | --------- | -------- | -------- |
| 4 | nMnCount | int | Deprecated | _Deprecated in Dash Core 0.12.3_<br><br>Number of masternode payment votes to request
{% highlight text %}
Note: Dash Core limits how frequently a masternode payment sync can be
requested. Frequent requests will result in the node being banned.
{% endhighlight %}
The following annotated hexdump shows a pre-0.12.3 `mnget` message. (The
message header has been omitted.)