|  Current phase: Rules Activated Block #162009
Finished
Change PoS Staking Algorithm
Agenda ID:  #sdiffalgorithm

Change stake difficulty algorithm as defined in DCP0001

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:
no
2.07%
yes
97.92%
Locked In:
141184
Activated:
149248
Hard Forked:
149328

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.

Finished
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:
no
1.38%
yes
98.61%
Locked In:
141184
Activated:
149248

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 95% of the 1000 most recent blocks must have the latest block version.
- For PoS, 75% of the votes cast within a static 2016 block interval must have the latest vote version.

The second phase is the voting itself. Voting takes place within a static 8064 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.

Visit our Documentation to learn more