Developers Declare Successful Completion of Final Shadow Fork
The Ethereum is nearing the Merge. In this scenario, the core developers of the network are making a lot of effort to guarantee that there are no problems. They are keen on the procedures related to as well as the function of the upcoming upgrade and Shadow fork. With the date of the Merge approaching closer, several tests have been carried out by the developers to confirm that the transition of Ethereum to proof-of-stake consensus goes smoothly.
The Conclusive Shadow Fork of Ethereum Accomplishes
According to the expectations, the Merge will take place in the coming week. The developers are of the view that they have been successful in carrying out the conclusive test to check the eligibility of the network to have the impending upgrade. The thirteenth shadow fork of Ethereum has now been accomplished without any hindrance, as pointed out by the developers. A shadow fork counts to be a trial-based operation that is done to demonstrate the potential expectations during the Merge upgrade.
The respective trial runs provide the ability to avoid any network exploitation or other likely problems. The Merge is anticipated to terminate the mining operations on Ethereum while the energy consumption will witness a drastic decrease by ninety-nine percent following the successful accomplishment of the procedure. During the tests that the network conducted, taking into account the above-mentioned, no problems have been found. This indicates that there is a high possibility for the upgrade to move per the strategy.
Bellatrix Upgrade Points out Significant Issues
In the previous week, the network additionally saw another important upgrade called the Bellatrix upgrade. There were some problems found during the respective upgrade. An upsurge of up to 1700% took place in the rate of the missed blocks. This is known as a metric indicating the rate of the network’s failure to validate a block.
The estimates discover that the blocks’ 0.5% proportion experience this problem. Nonetheless, with time, the very issue elevated to nine percent. The developers immediately elaborated the cause at the back of this as some node operators’ inability to update the consumers.
