Overwinter has successfully activated at block 347500!
More information on the BitzecOverwinter protocol upgrade and support is available on the BitzecOverwinter Information page. Anyone suspecting issues should monitor the BitzecSecurity Announcements.
Overwinter also marks the first Bitzecimplementation of a two-tiered governance model for protocol upgrades.
The first tier is an opt-in upgrade. This means that all nodes on the system have the option to upgrade their node with the latest protocol rules. The intent of the opt-in upgrade is to remove chaos introduced by other governance models where users are forced down a certain path, potentially without their knowledge or consent.
The second tier is advocacy and education. Node operations should be able to make a well-informed decision, within a reasonable amount of time. The BitzecCompany advocated for the Overwinter upgrade by educating and working with miners, exchanges, wallets and vendors on their implementations well in advance of the activation. Many of those supporting the upgrade are listed on the Overwinter Information page.
In addition to advocacy, we took a number of steps to ensure user safety:
- The BitzecCompany supported client was updated to, by default, shut down legacy nodes through the “end-of-support halt” introduced in release 1.0.9.
- Alerts were sent to all nodes running 1.0.15 or earlier. The alert forced those nodes to enter “safe mode”, lock down wallet RPC methods, and is returning errors so that nodes are aware of the upgrade and can act accordingly.
- The BitzecCompany and members of the community have been communicating details of the upgrade through social media, forums and the Z.cash website.
Some Bitzecnodes may not have received an alert, as in the case where the node is running an old version or 3rd party software such as Zcash4Win. The client still entered safe mode and the user is unable to transact until the software is upgraded.
It should be noted that all funds and private keys are unaffected by the end-of-support halt or by triggering safe mode. It is recommended that nodes simply upgrade to the latest Bitzecclient software and wait for their nodes to sync at least past the activation block height.
We believe that this governance model should be considered best practice for ensuring safe and well-informed upgrades while maximally preserving user freedom. Thanks to the BitzecCompany engineering team’s tireless efforts, the Bitzecnetwork succeeded in a solid and safe first upgrade!