Skip to content

DIP6: correct mn list entry calculation #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thephez merged 1 commit into from
May 16, 2022
Merged

DIP6: correct mn list entry calculation #111

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dip-0006.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ Each phase lasts for multiple blocks (quorumDkgPhaseBlocks) to ensure that all m
In this phase, the members of the new quorum are determined. This process is fully deterministic and results in exactly the same list seen by all members and observers.

1. Retrieve the deterministic masternode list which is valid at quorumHeight
2. Calculate `SHA256(SHA256(proTxHash, confirmedHash), SHA256(llmqType, quorumHash))` for each entry in the list
2. Calculate `SHA256(SHA256(proTxHash, confirmedHash), SHA256(SHA256(llmqType, quorumHash)))` for each entry in the list
* The `confirmedHash` is the block hash when a masternode registration is considered fully confirmed. For mainnet, this is the block where the masternode registration transaction has 15 confirmations. For other networks, only 1 confirmation is required. **_Note_**: The `confirmedHash` block must have one confirmation itself before `confirmedHash` can be used.
3. Sort the resulting list by the calculated hashes
4. Take the first quorumSize entries from this list and use the corresponding masternodes as members list
Expand Down