Ethereum customers are releasing a patch for a flaw that has affected the network

Ethereum developers have released a software update to fix block completion issues that have plagued the network’s Beacon Chain in the past days. Prysm and Teku clients, two of the most used clients on Ethereum, already have patches to fix the bug.

In a post known to the developer as superphiz.eth subscriber On Twitter, the Ethereum Foundation claimed this This “exceptional scenario” may be caused by the high load on some consensus layer clients, also called the beacon chain. However, they confirmed that they are still investigating the episode that prevented the blocks from being completed during periods 3 and 8 on two occasions: Thursday, May 11 and Friday, May 12.

Similarly, the organization that brings together major Ethereum developers confirmed that the network “continued to function, as it was designed, and users could continue to transact on it.” in this meaning, Decentralization at the consensus layer of the network was important, as not all clients were affectedstand out.

It can also be seen on the site clientdiversity.orgLighthouse, the most widely used client in the Ethereum consensus layer, has had no problems. The second and third with more nodes running them did, Prysm and Tiko, as reported by CriptoNoticias before the first of the two delay periods. One lasted 25 minutes and the other about an hour.

Prism developers explain

in it message In a recent update post, the Prysm team claimed that the new version “contains an improvement to prevent the Beacon chain from using too many resources during turbulent times.” “It is highly recommended to upgrade if your node is under heavy use,” they added.

On the other side, Written by Prism developer Terrence Cao string In which he gave details of the events of May 11 and 12.

Prysm nodes received many testimonials for previous reigns where the block did not reflect the last checkpoint in the fork election. Connected nodes may have sent the certificate without all blocks remaining for the rest of the epoch, causing Prysm to spend a lot of resources restoring the state, and eventually fell into a death spiral (CPU/OOM spikes).

Most customers, with the exception of Lighthouse, have encountered similar issues, Tsao says. However, according to the Ethereum Foundation statement, only Prysm and Teku have suffered these failures.

The Prysm team also admitted that there was a “hidden bug” in their nodes., as the correct condition was not used to calculate mixing during the ‘death spiral’ period. As a solution, they promised a new update for next week that corrects these shortcomings.

Clients and Complete Ban on Ethereum

Completion of blocks in a network that works with Proof of Stake (Proof of Stake or PoS) Refers to the process by which a block of transactions is deemed validated and confirmed through the network. Thus, it is definitively added to the accounting in the block chain.

To finalize a block on the POS network, validators must participate in the consensus process. If the majority agrees that the transactions are valid, the block is considered complete and is added to the blockchain permanently.

Validator nodes use clients to interact with the rest of the network. And thus be able to play their role in this process. Clients, then, are software applications that connect a node to Ethereum and allow users to send and receive transactions, as well as participate in the block verification process.