mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +00:00
Content - P2P - Note messages that will be deprecated by DIP3
This commit is contained in:
parent
c4e728c59f
commit
3910f56978
1 changed files with 18 additions and 1 deletions
|
@ -2498,6 +2498,9 @@ and [Masternode Payment](developer-guide#masternode<!--noref-->-payment) section
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
 NOTE: This message will be deprecated
|
||||
following activation of DIP3 which implements deterministic masternode lists.
|
||||
|
||||
The `dseg` message requests either the entire masternode list or a specific
|
||||
entry. To request the list of all masternodes, use an empty txIn (TXID of all
|
||||
zeros and an index of 0xFFFFFFFF). To request information about a specific
|
||||
|
@ -2544,6 +2547,9 @@ Masternode Unspent Outpoint
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
 NOTE: This message will be deprecated
|
||||
following activation of DIP3 which implements deterministic masternode lists.
|
||||
|
||||
The `mnb` message is sent whenever a masternode comes online or a client is
|
||||
syncing. The masternode will send this message which describes the masternode
|
||||
entry and how to validate messages from it.
|
||||
|
@ -2626,6 +2632,9 @@ Masternode Ping Message
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
 NOTE: This message will be deprecated
|
||||
following activation of DIP3 which implements deterministic masternode lists.
|
||||
|
||||
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.
|
||||
|
@ -2662,6 +2671,9 @@ a8170000 ................................... Count: 6056
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
 NOTE: This message will be deprecated
|
||||
following activation of DIP3 which implements deterministic masternode lists.
|
||||
|
||||
The `mnp` message is sent by masternodes every few minutes to ping the network
|
||||
with a message that propagates across the whole network. Dash Core currently
|
||||
uses a minimum masternode ping time of 10 minutes.
|
||||
|
@ -2822,6 +2834,9 @@ Masternode 2 Signature
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
 NOTE: This message will be deprecated
|
||||
following activation of DIP3 which implements deterministic masternode lists.
|
||||
|
||||
The `mnw` message is used to pick the next winning masternode. When a new block
|
||||
is found on the network, a masternode quorum will be determined and those 10
|
||||
selected masternodes will issue the masternode payment vote message.
|
||||
|
@ -2870,6 +2885,9 @@ Masternode Signature
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
 NOTE: This message will be deprecated
|
||||
following activation of DIP3 which implements deterministic masternode lists.
|
||||
|
||||
There is no message for `mnwb` (`inv` message only).
|
||||
|
||||
The following annotated hexdump shows an `inv` message with a `mnwb`
|
||||
|
@ -3141,7 +3159,6 @@ message header has been omitted.)
|
|||
|
||||
{% endautocrossref %}
|
||||
|
||||
|
||||
### Deprecated Messages
|
||||
{% include helpers/subhead-links.md %}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue