CyberWay Hardfork: the final announcement

Dear Validators and community members!

CyberWaydev team is pleased to announce that everything is ready for the very first HardFork in the CyberWay history!

The current HardFork applies changes to both node code and system contracts. Please find the list of transformations in the Release Notes, attached to GitHub tags:

1. CyberWay: https://github.com/cyberway/cyberway/releases/tag/v2.1.0 ( pay attention to the fact that minor changes were made to the “CHANGES IN THE NETWORK SUBSYSTEM” section, regarding what we published in https://golos.io/@cyberwaydev/cyberway-contracts-hardfork-announcement-1586792906485
2. Cyberway.cdt: https://github.com/cyberway/cyberway.cdt/releases/tag/v2.1.0
3. Cyberway.contracts: https://github.com/cyberway/cyberway.contracts/releases/tag/v2.1.0

HardFork itself is introduced with the execution of the following steps:

1. The node owners may upgrade them to v2.1.0 version. The docker-hub already contains a cyberway/cyberway:v2.1.0 image. No node replay of the block log is required to update the node.

2. Validators may sign proposals for updating system contracts after updating their nodes These offers can be found inside the explorer using the following addresses:

• cyber, status: waiting, created: 4/20/2020, 11:28:06 PM, block #6707314 - Cyber contract update
• token, status: waiting, created: 4/20/2020, 11:35:24 PM, block #6707452 - Cyber.token contract update
• msig, status: waiting, created: 4/20/2020, 11:36:18 PM, block #6707469 - Cyber.msig contract update
• stake, status: waiting, created: 4/20/2020, 11:36:48 PM, block #6707479 - Cyber.stake contract update
• govern, status: waiting, created: 4/20/2020, 11:37:06 PM, block #6707485 - Cyber.govern contract update
• domain, status: waiting, created: 4/20/2020, 11:37:24 PM, block #6707491 - Cyber.domain contract update
• initautorc, status: waiting, created: 4/20/2020, 11:37:42 PM, block #6707497 - initialization of the voice reset mode for validators. Invoking an action from this transaction allows cyber.stake: setautorcmode to be executed on behalf of validators, also allowing the users to configure an automatic reset of the votes for validators for the CYBER token.

3. CyberWaydev team will send them for execution as soon as the required number of signatures is collected to fulfill the proposals.

4. 2 weeks after these 3 steps described above, new versions of contracts will be installed and the nodes will switch to updated performance algorithms.

Attention!

• The node is continuing to work in accordance with the old rules straight after the upgrade procedure is conducted. New rules come into play only after updating the system contracts. However, changes in the network subsystem associated with the exchange of IP-addresses of seed-nodes will be available immediately.
• The nodes pertaining to the old version (up to v2.0.3) will not be able to function correctly after updating the system contracts, as the new version contains a list of changes necessary to support the updated version of the contracts.

Don't hesitate to join our community via:

Commun:

https://commun.com/cyberway

Telegram:

• CyberWay - https://t.me/cyberway_en (for general questions and inquiries)
• CyberWay Validators - https://t.me/cyberway_validators_en (for questions and inquiries concerning validators of CyberWay platform)
• CyberWay Dev - https://t.me/cyberway_dev (for instant technical feedback from our Dev team)

Twitter:

We'll keep you updated over https://twitter.com/cyberwayio

Best regards, @cyberwaydev team: @andreypf, @marina, @maslenitsa, @muhazokotuha, @zxcat, @annaeq, @anazarov79, @kaynarov, @s-medvedev, @eugin