Upgrade Threshold: 75%
Rolling Window: 100 Blocks
Next Version: v11
Upgrade Threshold: 75%
Rolling Window: 100 Blocks
Upgrade Threshold: 75%
Upgrade Interval: 1,153,920 - 1,155,936
Upgrade Threshold: 75%
Upgrade Interval: 1,153,920 - 1,155,936
Enable features defined in DCP0002 and DCP0003 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.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Modify sequence lock handling as defined in DCP0004
In order to fully support the Lightning Network, the current sequence lock consensus rules need to be modified.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Enable header commitments as defined in DCP0005
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.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Enable decentralized Treasury opcodes as defined in DCP0006
In May 2019, Decred stakeholders approved the development of a proposed solution to further decentralize the process of spending from the Decred treasury.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Change maximum treasury expenditure policy as defined in DCP0007
Change the algorithm used to calculate Treasury spending limits such that it enforces the policy originally approved by stakeholders in the Decentralized Treasury proposal.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Enable explicit version upgrades as defined in DCP0008
Modifications to Decred transaction and scripting language version enforcement which will simplify deployment and integration of future consensus changes across the Decred ecosystem.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Enable automatic ticket revocations as defined in DCP0009
Changes to ticket revocation transactions and block acceptance criteria in order to enable automatic ticket revocations, significantly improving the user experience for stakeholders.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Change proof of work hashing algorithm to BLAKE3 as defined in in DCP0011
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).
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Change block reward subsidy split to 1/89/10 as defined in DCP0012
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%.
The new rules have been activated. Ensure you are running a recent enough software version that supports the new rules. Visit our Downloads Page to get the latest Software.
Voting Overview
There is a two-phase process for voting to implement consensus changes that would create a hard fork.
The first Phase is meeting the upgrade threshold on the network. A majority of PoS/PoW nodes on the network must upgrade before voting can begin. This is measured in the following ways:
- For PoW, at least 75% of the 100 most recent blocks must have the latest block version.
- For PoS, 75% of the votes cast within a static 2,016 block interval must have the latest vote version.
The second phase is the voting itself. Voting takes place within a static 5,040 block interval. If 75% of votes mined within that interval signal a ‘yes’ vote to the proposals, the changes are implemented. Implementation happens after one additional block interval to allow any remaining nodes to update prior to the fork.