- But the real cause of the failure is still unknown.
- Prysm and Teku clients have already installed the patch
Last week, on May 11 and 12, for some time, user transactions in Beacon Chain were not processed to the end. And if the first time the failure lasted 25 minutes, then the second time it lasted an hour. Over the weekend, the developers finally rolled out a patch.
It has been deployed to the Ethereum Prysm and Teku clients. This is how the Ethereum Foundation commented on the situation:
“It happened because of the diversity of clients. The problem did not affect all versions, but when they “caught up” with the rest, a new failure occurred.
See also “Superphiz.eth” eleveteal following:
“We can finally put this situation behind us. Prysm and Teku customers have installed an update to prevent the attestation flood. I believe that this is another step not only towards decentralization, but also towards diversity. Let’s draw conclusions and move on.”
Notably, under this ‘tweet’, some users asked for clarification on the ‘exceptional scenario’ referred to by ‘Superphiz.eth’. However, he ignored them.
The ecosystem development fund explained that the failure arose due to the high load on individual clients at the consensus level. But the organization does not know what caused it.
The problem with transaction processing is another reminder that Beacon Chain is still being finalized. Although such a prompt reaction of the developers indicates careful preparation and a high level of professionalism, analyst Arnold Tokh believes.