joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 01:36:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Content - superblock clarify (#126)

Browse source 
* Content - Additional info regarding superblocks

* Content - Clarify superblock details

* Apply suggestions from code review

Co-Authored-By: thephez <thephez@users.noreply.github.com>

* Typo fix

* Update _includes/devdoc/guide_dash_features.md

Co-Authored-By: thephez <thephez@users.noreply.github.com>

* Formatting
This commit is contained in:
thephez 2019-05-02 08:14:27 -04:00 • committed by GitHub
parent adc9232b72
commit a9f147c6b9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
_includes/devdoc/guide_dash_features.md
View file

@ -730,6 +730,23 @@ voted to delete them.
Sentinel manages superblock creation, voting, and submission to dashd for
network propagation.
Beginning ~3 days (1662 blocks) prior to a superblock, Sentinel selects one
masternode per block to rank proposals. This ranking is used to determine
what a candidate superblock (or "superblock trigger") should contain. Based on
the results, it creates and broadcasts a new superblock trigger if a matching
one was not found.
All masternodes vote for existing superblock triggers. Each masternode casts
only 1 superblock trigger "Yes" vote per superblock cycle. It will vote "No"
for any other triggers it receives.
Note: This means that proposal votes submitted _after_ superblock trigger
creation begins will _not_ be counted by some masternodes (those that have
already voted on a superblock trigger).
At the superblock height, the trigger with the most "Yes" votes is paid out by
that block's miner.
##### Sentinel<!--noref--> Ping
{% include helpers/subhead-links.md %}