feat(platform)!: contested document resolution with masternode voting #1878
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shumkov
force-pushed
the
feat/contestedDocumentResolutionWithMasternodeVoting
branch
from
fbbc8da to
f6b572f
Compare
QuantumExplorer
force-pushed
the
feat/contestedDocumentResolutionWithMasternodeVoting
branch
from
f6b572f to
2d30333
Compare
lklimek
changed the title
Co-authored-by: Quantum Explorer <[email protected]>
…tender in a contest twice. (#1923)
Co-authored-by: Quantum Explorer <[email protected]> Co-authored-by: pauldelucia <[email protected]> Co-authored-by: Paul DeLucia <[email protected]> Co-authored-by: Ivan Shumkov <[email protected]>
QuantumExplorer
changed the title
…f github.com:dashpay/platform into feat/contestedDocumentResolutionWithMasternodeVoting
…ionWithMasternodeVoting # Conflicts: # Cargo.lock
Temporary disabled due to flakiness. These tests aren't important for now, since we are // going to release v1.0.0 with withdrawals disabled.
6 tasks
QuantumExplorer
deleted the
feat/contestedDocumentResolutionWithMasternodeVoting
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
A unique index might be coveted by multiple identities making it valuable. Since it is valuable we need a way to distribute such value.
What was done?
This proposal implements a workable DAO type voting mechanisms to distribute contested unique indexes.
A document type can have at most 1 contested unique index.
This contested unique index can have a match field. If we insert a document that matches the field of the contested unique index then a contest is started. The cost to be a contender in a contest is hard coded in v1 at 0.2 Dash.
Other identities can join this contest for up to 1 week.
The contest lasts for 2 weeks total.
Masternodes and Evonodes can vote in a contest, they can change their votes up to 4 times. There is a specialized balance pool that they use to pay for fees.
Masternodes and Evonodes can vote for a contender, or they can abstain or vote to lock the vote. If the lock vote wins, no document is awarded.
Locked polls can eventually be unlocked (not part of this PR) by paying 2 Dash to restart the contest, if this is the case, the threshold to win the vote must be at least 50 votes.
At the end of the contest the document is awarded to the winner.
There is a clean up mechanism to remove extra data from the state at finalization of the vote.
Masternodes that move their collateral have their votes removed.
Sum trees are used to give efficient vote totals.
Masternodes have a weight of 1, Evonodes have a weight of 4.
SDK now includes
How Has This Been Tested?
Many unit tests were made.
Breaking Changes
This includes many breaking changes.
Checklist:
For repository code-owners and collaborators only