HardFork v2.1.0 results and Validators activity review May 7-14 / COMMUN GRANT PROGRAMME
Hooray! @Cyberwaydev team is pleased to announce the successful completion of the first ever HardFork committed in the CyberWay network. All the proposals listed in a previous post were signed and successfully completed on May 11, 2020, 1:17:09 PM. Lets recall the main changes briefly:
validators who start missing blocks regularly do not receive a reward; if a validator does not generate blocks within a week, he gets excluded from the schedule
now is possible to add a description of the proposal in the contract cyber.msig, and the transaction itself is to be performed as a delayed transaction.
a bug connected to the loss of CYBER untrusted tokens was fixed, and the funds were returned to accounts, go check https://explorer.cyberway.io/trx/e82b47b455bbd3f794948b665a3daf19d72332c8816801fdac72d322a214eb60
changes are made to the network subsystem, thanks to which the servers actively exchange seed addresses.
Head over to Release Notes for explicit info about all the changes applied:
- https://github.com/cyberway/cyberway/releases/tag/v2.1.0 and
- https://github.com/cyberway/cyberway.contracts/releases/tag/v2. 1.0.
Attention! Validators @xtar and @cryptocode were dismissed and disqualified since HF v2.1.0 came into power.
And now let’s dive into our weekly activities
Blocktivity stats
an activity chart drawing the users’ attention to the real performance of chains
Please note that we’re making adjustments to our block explorer on a regular basis. Don’t hesitate to reach out to us with any interface-related suggestions.
You can hop into our block explorer (https://explorer.cyberway.io/validators) at any time to track the productivity of validators. Each of our reports is to provide you with the most recent and coherent data for the last 7 days.
Attention! Take a moment to check out Commun community grants programme we’ve announced earlier this week! Don’t hesitate to contact @marina or @annaeq for submitting your info! Let's grow together :)
Any suggestions/proposals regarding our validator portal? Hit @annaeq via Telegram to convey your ideas.
Please note! The public seed nodes are extremely important to CyberWay. Having them in abundance does increase the resiliency of the network infrastructure and ensures smooth and reliable work of the network even in case force-majeure events leading to a shutdown of existing seed nodes (e.g., as a result of an accident / economical factors or legal problems / natural disasters / as a matter of disconnection / human factor / etc.).
Dear Validators! Help CyberWay expand by setting a seed node on your own. Send the addresses of your seed nodes in the form of a pull-request to the public list:
https://github.com/cyberway/cyberway.launch/blob/master/seednodes
Don't hesitate to join our community via:
Commun:
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