{"id":70664,"date":"2020-10-16T19:43:29","date_gmt":"2020-10-16T19:43:29","guid":{"rendered":"https:\/\/wp.dash.org\/uncategorized\/v0-16-migration-report-week-2\/"},"modified":"2021-09-23T14:57:41","modified_gmt":"2021-09-23T14:57:41","slug":"v0-16-migration-report-week-2","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/blog\/v0-16-migration-report-week-2\/","title":{"rendered":"v0.16 Migration Report \u2014 Week 2"},"content":{"rendered":"
Dash Core v0.16.0.1 was released on Wednesday, September 30th, the first release of v0.16.x.<\/p>\n
Please see the updated product brief<\/a> to learn about the main improvements in v0.16 or the Release Notes<\/a> for the detailed set of changes.<\/p>\n Friday October 16th marks just over two weeks since the release of v0.16.0.1, and I would like to share some statistics and information about the migration.<\/p>\n Note: v16 is a mandatory upgrade for everyone<\/strong>: miners, masternodes and users! Once the hard fork activates and the diverging block is mined, outdated clients will no longer follow the main chain.<\/p>\n In just over two weeks, 66% of all masternodes have been upgraded to v0.16.0.1. This is up 16% in the last week. This is good progress, and we would like to thank all the MNOs for taking the time to upgrade promptly.<\/p>\n I\u2019m very hopeful that we can hit 80% by next week!<\/p>\n Version 0.16 includes a BIP9 activated hard fork. The activation works in periods or \u201cwindows\u201d of 4032 blocks. The second window opened at block 1354752, and was mined on 2020\u201310\u201314 21:40:16 UTC. This window is roughly ~7.35 days long and would require ~79.8% of the miners to upgrade for the hard fork to \u201cLock in\u201d. Each subsequent window reduces the threshold slightly, until it reaches 60% in 10 windows. The exact threshold schedule can be found here<\/a>.<\/p>\n At the time of writing, several pools have already mined blocks signalling support of the upgrade. <\/strong>About 1000 blocks into this window, 9% of blocks have signaled for the upgrade. In the last 24 hours about 11% signaled for the upgrade.<\/p>\n We encourage all miners to test this new release and begin upgrading your systems to v0.16.0.1.<\/p>\n In this release, two new sporks have been added, Spork 21 and Spork 22.<\/p>\n Spork 21 enables minimum protocol checks and LLMQ concentrated recovery. Spork 21 will be activated approximately seven days after 80% of the masternodes have upgraded to ensure that all MN operators have sufficient time to upgrade their node(s). Once Spork 21 is activated, non-upgraded nodes will begin to be Proof of Service (PoSe) banned. A more exact date will be announced once this threshold has been met.<\/p>\n The timeline for Spork 22, which bumps the maximum number of participants in a round of PrivateSend to 20, will be specified in a future post.<\/p>\nMasternode Upgrade Progress<\/h2>\n
Miner Upgrade Progress<\/h2>\n
Spork Activation and old Masternode PoSe banning<\/h2>\n