Some of the key developers on Ethereum’s blockchain are contemplating the current preparation process in place for the biggest upgrade to take place in years. Particularly, some developers are calling for cautious approaches to future forks.
One of the major providers of Ethereum’s software, Parity Technologies, severely struggled to prepare for the upgrade deadlines. Parity takes up about 25 percent of the whole network and discovered an array of bugs within their current software leading up to the weekend. Developers worked throughout the weekend to get these conflicts resolved, trying to avoid any need for a potential delay.
Parity founder and CTO, Gavin Wood, has finally spoken out on the issues his team faced and states the upgrading process has many “lessons to be learned.”
CoinDesk requested further comments from Wood in regards to the success of Byzantium, He voiced his caution in the danger zone around the hard fork and how it could last for several days.
Looking towards the future, he says that he feels that more prudent approaches should be implemented to make sure that every client is ready for such a big shift.
Wood told CoinDesk:
“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 explain that most software users were given little to no time to make the big upgrades just before the fork.
Developers continued their work and began encountering countless bugs within the software that put them in a hard position to make a choice.
“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.
Wood had a few suggestions on preparations for future updates including a smart contrast to “dynamically postpone” a problematic hard fork or developing weekend retreats with the various software providers to gear them up.
As none of his suggested steps were put into play this time, Wood suggests users proceed with caution in the weeks ahead.
“I’m generally optimistic that even if further ‘zero-day consensus’ problems are found by our auditors and tools, we can roll out the antidote upgrades before they become problematic,” he said.
Featured Image: pixabay