Ethereum Core Devs Discuss Benefits Of Frequent Hard Forks
A certain group involving a number of veterans of Ethereum’s open-source developers talked about the idea of how often the altering of consensus should be. During the meeting, they talked about the possibility of having system-wide upgrades – also known as hard forks.
Leveraging Hard Forks
According to the official report, these hard forks can be utilized directly to software. Even more so, the aforementioned veterans are looking at the possibility of enacting them for every three months (although nothing official has been set on stone yet).
One of the developers ponders on the idea of requiring a handful of upgrades sequentially, one that can space out in full effect. Interestingly, this is all for the goal of checking the temperatures.
But as far as Joseph Delong, the senior software engineer at Consensys, it is rather a very quick turnaround. It is worth noting that the company is dubbed a venture capital studio.
An Utmost Concern
As for Péter Szilágyi, a team lead at the Ethereum Foundation, he agrees with Delong’s idea. He said that as software client developer, developing and implementing hard works should be fine when done within three months. However, it should be noted that all clients tend to require a variety of maintenance – all of which must be accomplished. He added that if one has to perform three months of hard forks, there is no doubt that it will require all the much-needed time, especially when it comes to general maintenance and performance improvements.
Martin Hoste Swende, the Ethereum Foundation security lead, on the other hand, agreed with the idea of at least three months of hard work. The only catch, according to him, is that could really be “a bad thing.” He even went to introduce a couple of simple changes, all of which can be unanimously agreed right away even after having shorter run times.
For Swende, it is not all about scheduling hard forks every three months. It is rather about seeing the possibility of feature X to be completed. And if there is a test that can exist, it must necessarily be implemented in all concerning clients. Only by then, as per Swende, can they all implement hard forks with ease. The only thing, however, is that encouraging developers to perform their plans accordingly is impossible to achieve – event at a timeline of at least six months.