joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-28 10:16:15 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Guide - Update MN payment description

Browse source 
Related to dashpay/dash#2258
This commit is contained in:
thephez 2018-12-18 11:47:19 -05:00
parent f5a3097aad
commit de08d26898
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
_includes/devdoc/guide_dash_features.md
View file

@ -302,6 +302,20 @@ value of only 0.00000546 DASH as shown by the calculation below.
{% autocrossref %} {% autocrossref %}
Since DIP3 (introduced in Dash Core 0.13.0), masternode reward payments are based
on the deterministic masternode list information found on-chain in each block.
This results in a transparent, deterministic process that operates using the
[algorithm described in DIP3](https://github.com/dashpay/dips/blob/master/dip-0003.md#masternode-rewards).
On-chain masternode lists reduce the complexity of reward payments, make
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 Masternode payment uses a verifiable process to determine which masternode is
paid in each block. When a new block is processed, a quorum of paid in each block. When a new block is processed, a quorum of
`MNPAYMENTS_SIGNATURES_TOTAL` (10) masternodes vote on the next masternode `MNPAYMENTS_SIGNATURES_TOTAL` (10) masternodes vote on the next masternode