NEWSLETTER
ethereum developers (eth) are configured to launch Hoodi, a new long -term testnet, on March 17 while working to solve continuous challenges with the highly anticipated sicking update.
The testnet's net will focus mainly on the validader exit mechanisms, one of the final obstacles before pein can advance. The broader tests will continue in the Bolia and Holesky balls of ethereum.
The tong update, which combines characteristics of the proposals of Prague and Electra, aims to improve betting operations, improve execution and consensus layers and introduce key optimizations for ethereum validators.
However, the update has faced repeated delays due to customer preparation problems, synchronization errors and infrastructure concerns.
According to the developer of the ethereum Foundation, Tim Beiko, the activation of Mainnet's Pin will only continue if Hoodi successfully is bifurcators and customer teams confirm confidence in the stability of the update.
Even in the best case, Mainnet activation will not occur until at least 30 days after the forks, establishing April 25 as the earliest possible date.
Pectra fights
ethereum developers have been working through a series of unexpected challenges, including problems with validator outputs, network synchronization and compatibility between customer implementations.
Delays come from the problems found during Testnet implementations. The Holesky Testnet, for example, could not finish after the sicking update, which led to possible delays in the launch of Mainnet as developers investigate the problems.
Similarly, the sepolia Testnet experienced erroneous configurations, which led the developers to extend the trial period to collect more data before continuing with the activation of Mainnet.
In addition, some client teams have expressed concern about last -minute changes within reach of the update, which has complicated the test process. ethereum's modular development structure means that updates should be coordinated in multiple teams that work in different execution and consensus clients, which adds to complexity.
The ethereum community has expressed mixed reactions to recent delays in the sicking update. While some members are frustrated by the postponements, others appreciate the cautious approach of developers to guarantee the stability of the network.
Despite these setbacks, many members of the community remain optimistic about the potential benefits of pein, including the best flexibility of rethinking and improved scalability
Fasting update
While pein it is still a priority, ethereum developers are also progressing with the planning of the Fusaka update, which will continue to pert.
Fusaka will enter the sampling of pairs data (peerdas) to improve data management by allowing validators to show data instead of downloading complete data sets, reducing bandwidth requirements.
It also implements the Virtual Machine Object format ethereum (EOF) to optimize the execution of the smart contract by enabling the separation and code data versions, reducing costs for developers.
The ethereum central team has established a deadline of March 24 for the proposals for improvement of ethereum (EIP) to be considered for inclusion. Customer teams are expected to share their scope preferences before March 31, with a freezing freezing established for April 10.
ethereum developers remain committed to guaranteeing a stable and safe network update. However, multiple delays with pein underline the growing difficulty of coordinating large -scale changes to ethereum infrastructure as it continues scale.
Mentioned in this article
