From ccaf9bdd29ec7c62d75fc4c91a27c7ba7d73abb6 Mon Sep 17 00:00:00 2001 From: thephez Date: Mon, 16 Sep 2019 09:50:04 -0400 Subject: [PATCH] Content - move old MN payment description to historical reference --- _includes/devdoc/guide_dash_features.md | 55 +++++++++++++++---------- 1 file changed, 34 insertions(+), 21 deletions(-) diff --git a/_includes/devdoc/guide_dash_features.md b/_includes/devdoc/guide_dash_features.md index 5d29a504..6474a4f3 100644 --- a/_includes/devdoc/guide_dash_features.md +++ b/_includes/devdoc/guide_dash_features.md @@ -317,27 +317,6 @@ payments much more predictable, and also allow masternode payments to be enforced for all blocks (enforcement for superblocks was not possible in the previous system). -**Historical Note** - -Prior to DIP3, the masternode payment process operated as described below. - -Masternode payment uses a verifiable process to determine which masternode is -paid in each block. When a new block is processed, a quorum of -`MNPAYMENTS_SIGNATURES_TOTAL` (10) masternodes vote on the next masternode -payee. The quorum is calculated deterministically based on the distance between -masternode's hash and the block's proof of work. - -Each member of the quorum issues a 'mnw' message that is relayed to the -network. The payee is selected from a subset of masternodes made up of 10% -of eligible nodes that have been waiting the longest since their last payment. -The winner is then determined based on a number of parameters including the -distance between the its hash and the block's proof of work. For additional -detail, reference this [Official Documentation Payment Logic page](https://docs.dash.org/en/0.12.3/masternodes/understanding.html#payment-logic). - -Nodes receiving a `mnw` message verify the validity of the message before -relaying it to their peers. If the message is invalid, the sending node may be -treated as misbehaving and have its ban score increased. - {% endautocrossref %} ### Masternode Sync @@ -825,6 +804,40 @@ had already been confirmed to a block depth of 5 in the blockchain. {% endautocrossref %} +#### Masternode Payment (original) +{% include helpers/subhead-links.md %} + +![Warning icon](/img/icons/icon_warning.svg) **The following information is for +historical reference only. It describes the masternode payment process that was +used prior to the deterministic masternode list update in Dash Core v0.13 that +implemented DIP3.** + +Please see [here for details of the current system](#masternode-payment) + +{% autocrossref %} + +Prior to DIP3, the masternode payment process operated as described below. + +Masternode payment uses a verifiable process to determine which masternode is +paid in each block. When a new block is processed, a quorum of +`MNPAYMENTS_SIGNATURES_TOTAL` (10) masternodes vote on the next masternode +payee. The quorum is calculated deterministically based on the distance between +masternode's hash and the block's proof of work. + +Each member of the quorum issues a 'mnw' message that is relayed to the +network. The payee is selected from a subset of masternodes made up of 10% +of eligible nodes that have been waiting the longest since their last payment. +The winner is then determined based on a number of parameters including the +distance between the its hash and the block's proof of work. For additional +detail, reference this [Official Documentation Payment Logic page](https://docs.dash.org/en/0.12.3/masternodes/understanding.html#payment-logic). + +Nodes receiving a `mnw` message verify the validity of the message before +relaying it to their peers. If the message is invalid, the sending node may be +treated as misbehaving and have its ban score increased. + +{% endautocrossref %} + + #### Masternode Sync (original)