Two consensus clients have been released on Ethereum 2.0, Prysm and Teku new upgrades to address current The definitive beacon series problems.
Ethereum network face final problems twice in 24 hoursthe first for 25 minutes and second permanent more from hour.
According to a announcement on Ethereum Foundation Blog, on On May 11th and 12th, there were two different events where the evidence was-of- Consensus Mechanism (PoS) for Ethereum network Beacon chain failed to get to the end for 3 and 8 periods, respectively.
However, end-user transactions were not affected due to the diversity of clients because not all client implementations were affected by the occurrence.
exactly cause of the problem still under investigation; However, it looks like heavy loads on some of Consensus layer clients triggered Through an “extraordinary scenario” it may be caused the issue.
Prism and Tico announce promotions
Meanwhile, Prysm and Teku are released new Updates that include modifications to prevent beacon nodes from consuming excessive amounts of during these exceptional scenarios.
Prism updatev4.0.3 – dubbedfix contains the necessary optimization to prevent the Beacon Chain node from consuming too many resources during periods of disruption.
ETH 2.0 client urges Ethereum node administrators to upgrade their nodes if it is a critical resource use It is happening.
On the other hand, Teku’s v23.5.0 update removed Outdated and questionable certificates from the Ethereum mainnet. the update also Kit included changes and reinforcements designed To prevent flooding issues similar certification in the future.
Other Ethereum clients, such as Nimbus, have claimed required There are no core upgrades for their clients. However, they have indicated that they will continue to monitor issue and saving fixes If it gets worse.
For their part, Lighthouse and Lodestar have seen a potential burden due to unique building. While other ETH 2.0 clients consumed a large number of amount of Resources, the two kept b network alive checks 40-50% of Until other clients recover and start checking blocks.
You must log in to post a comment.