Consensus Vote Archive
This section provides an archive for previous votes along with their outcomes.
Vote version 10
The upgrade to vote version 10 was included in dcrd 1.8.0 released on 13 June 2023.
Voting Start | Voting End | Activated |
---|---|---|
778,240 | 786,303 | 794,368 |
Change PoW to BLAKE3 and ASERT
Agenda ID: blake3pow
Change proof of work hashing algorithm to BLAKE3 as defined in in DCP-0011
Stakeholders voted to change the Proof-of-Work hash function to BLAKE3. This consensus change will also update the difficulty algorithm to ASERT (Absolutely Scheduled Exponentially weighted Rising Targets).
Voting Results
Choice | Percentage |
---|---|
Abstain | 35.52% |
No | 0.34% |
Yes | 64.13% |
Change PoW/PoS Subsidy Split To 1/89
Agenda ID: changesubsidysplitr2
Change block reward subsidy split to 1/89/10 as defined in DCP-0012
Modify the block reward subsidy split such that 1% goes to Proof-of-Work (PoW) and 89% goes to Proof-of-Stake (PoS). The Treasury subsidy remains at 10%.
Voting Results
Choice | Percentage |
---|---|
Abstain | 36.59% |
No | 0.45% |
Yes | 62.95% |
Vote version 9
The upgrade to vote version 9 was included in dcrd 1.7.0 released on 20 January 2022.
Voting Start | Voting End | Activated |
---|---|---|
641,152 | 649,215 | 657,280 |
Revert Treasury Expenditure Policy
Agenda ID: reverttreasurypolicy
Change maximum treasury expenditure policy as defined in DCP-0007
Change the algorithm used to calculate Treasury spending limits such that it enforces the policy originally approved by stakeholders in the Decentralized Treasury proposal.
Voting Results
Choice | Percentage |
---|---|
Abstain | 41.30% |
No | 0.03% |
Yes | 58.66% |
Explicit Version Upgrades
Agenda ID: explicitverupgrades
Enable explicit version upgrades as defined in DCP-0008
Modifications to Decred transaction and scripting language version enforcement which will simplify deployment and integration of future consensus changes across the Decred ecosystem.
Voting Results
Choice | Percentage |
---|---|
Abstain | 41.68% |
No | 0.03% |
Yes | 58.28% |
Automatic Ticket Revocations
Agenda ID: autorevocations
Enable automatic ticket revocations as defined in DCP-0009
Changes to ticket revocation transactions and block acceptance criteria in order to enable automatic ticket revocations, significantly improving the user experience for stakeholders.
Voting Results
Choice | Percentage |
---|---|
Abstain | 41.69% |
No | 0.03% |
Yes | 58.27% |
Change PoW/PoS Subsidy Split
Agenda ID: changesubsidysplit
Change block reward subsidy split to 10/80/10 as defined in DCP-0010
Proposal to modify to the block reward subsidy split such that 10% goes to Proof-of-Work and 80% goes to Proof-of-Stake.
Voting Results
Choice | Percentage |
---|---|
Abstain | 39.79% |
No | 0.15% |
Yes | 60.14% |
Vote version 8
The upgrade to vote version 8 was included in dcrd 1.6.0 released on 21 January 2021.
Voting Start | Voting End | Activated |
---|---|---|
536,320 | 544,383 | 552,448 |
Enable Decentralized Treasury
Agenda ID: treasury
Enable Decentralized Treasury as defined in DCP-0006
In May 2019, Decred stakeholders approved the development of a proposed solution to further decentralize the process of spending from the Decred treasury.
Voting Results
Choice | Percentage |
---|---|
Abstain | 16.72% |
No | 0.08% |
Yes | 83.18% |
Vote version 7
The upgrade to vote version 7 was included in dcrd 1.5.0 released on 29 January 2020.
Voting Start | Voting End | Activated |
---|---|---|
415,360 | 423,423 | 431,488 |
Enable Block Header Commitments
Agenda ID: headercommitments
Enable header commitments as defined in DCP-0005
Proposed modifications to the Decred block header to increase the security and efficiency of lightweight clients, as well as adding infrastructure to enable future scalability enhancements.
Voting Results
Choice | Percentage |
---|---|
Abstain | 38.74% |
No | 0.03% |
Yes | 61.21% |
Vote version 6
The upgrade to vote version 6 was included in dcrd 1.4.0 released on 5 February 2019.
Voting Start | Voting End | Activated |
---|---|---|
326,656 | 334,720 | 342,784 |
Update Sequence Lock Rules
Agenda ID: fixlnseqlocks
Modify sequence lock handling as defined in DCP-0004
In order to fully support the Lightning Network, the current sequence lock consensus rules need to be modified.
Voting Results
Choice | Percentage |
---|---|
Abstain | 45.52% |
No | 0.00% |
Yes | 54.46% |
Vote version 5
The upgrade to vote version 5 was included in dcrd 1.1.0 released on 22 September 2017.
Voting Start | Voting End | Activated |
---|---|---|
173,440 | 181,504 | 189,568 |
Activation of new opcodes for Lightning Network Support
Agenda ID: lnfeatures
Enable features defined in DCP-0002 and DCP-0003 necessary to support Lightning Network (LN)
The Lightning Network is the most directly useful application of smart contracts to date since it allows for off-chain transactions that optionally settle on-chain. This infrastructure has clear benefits for both scaling and privacy. Decred is optimally positioned for this integration.
Block 205189 is the first block which contains the new opcode which was voted in via the lnfeatures vote and thus all old nodes must upgrade.
Voting Results
Choice | Percentage |
---|---|
Abstain | 37.70% |
No | 0.30% |
Yes | 61.98% |
Vote version 4
The upgrade to vote version 4 was included in dcrd 1.0.0 released on 26 April 2017.
Voting Start | Voting End | Activated |
---|---|---|
133,120 | 141,184 | 149,248 |
Change PoS Staking Algorithm
Agenda ID: sdiffalgorithm
Change stake difficulty algorithm as defined in DCP-0001
Specifies a proposed replacement algorithm for determining the stake difficulty (commonly called the ticket price). This proposal resolves all issues with a new algorithm that adheres to the referenced ideals.
Voting Results
Choice | Percentage |
---|---|
Abstain | 12.23% |
No | 1.81% |
Yes | 85.94% |
Start Lightning Network Support
Agenda ID: lnsupport
Request developers begin work on Lightning Network (LN) integration
The Lightning Network is the most directly useful application of smart contracts to date since it allows for off-chain transactions that optionally settle on-chain. This infrastructure has clear benefits for both scaling and privacy. Decred is optimally positioned for this integration.
Voting Results
Choice | Percentage |
---|---|
Abstain | 22.58% |
No | 1.07% |
Yes | 76.34% |