Header Ads

Trust God

Ethereum's Gavin Wood......... Calling for More 'Coordinated' Hard Forks

parity, wood

The last Ethereum hard fork and the process of upgrading the blockchain may have come and gone, but that doesn't mean notable developers aren't reflecting on the processes leading to the Fork.

There seem to be a consensus about getting major stakeholders ready before any fork, for instance, while the update appears to have been successful, at least one provider of Ethereum software notably struggled with preparations for the rollout. UK-based Parity Technologies, used by nearly 25 percent of the network, was beset with bugs through the weekend, a development that spurred speculation about last-minute delays.

But while that specter has been avoided, Parity founder and CTO Gavin Wood is now speaking out on the issues, citing the upgrade process as one that is rife with "lessons to be learnt" for the community of developers working on the second-largest blockchain by total value.

In response to requests for comment, Wood outlined his belief that it is perhaps too early to deem the so-called Byzantium code upgrade a successful one, noting the danger zone around a hard fork can extend for several days. Looking ahead, he said he feels that more foresight should be put into whether client software providers are ready to make the shift.

"There needs to be a more conservative approach to the specification, development, testing and deployment for major protocol alterations like Byzantium... It should be ascertained to as great a degree as possible that all major implementations are in consensus before any determination of a hard fork block."

Wood went on to use this most recent fork as evidence, describing it as a situation in which most software users were asked to make big upgrades with little time to do so.

As continued bugs were discovered, he said developers ultimately had to make a difficult choice, one of the reasons it remains to be seen just how smooth the rollout will prove.

"It was really a choice between requiring most users change their software within 48-72 hours to postpone the fork versus possibly or probably requiring a particular subset of the network to update their software at a much shorter notice should a problem be discovered," he explained.

Building on this, Wood went on to propose a number of changes he might favor, including scheduling retreats with various software providers or using smart contrast to "dynamically postpone" a problematic hard fork.

Still, as these steps weren't taken this time around, he advised caution for those using the network in the days and weeks ahead.

Friend, Jesus came looking for you. Give your heart to Him, Love the Lord with all your heart, strength and might.  Love your neighbour as yourself, hold no offence, no bitterness - the Lord is near you to help you!


Powered by Blogger.