- But the true cause of the failure is still unknown
- Prysm and Teku customers have already installed the patch
In the past week, May 11 and 12, user transactions in Beacon Chain were not fully processed for some time.
And if the first time the failure lasted 25 minutes, the second time it lasted an hour. Over the weekend, the developers finally rolled out a patch.
It was rolled out to the Ethereum Prysm and Teku clients. This is how the Ethereum Foundation commented on the situation:
“It happened because of customer diversity. Not all versions were affected, but when they “caught up” with the others, there was another crash.”
Superphiz.eth also noted the following:
“We can finally put this situation behind us.. Prysm and Teku clients have installed an update to prevent attestation flooding.
I believe that this is another step not only toward decentralization, but also toward diversity. Let’s draw conclusions and move on.”
It is noteworthy that under this “tweet,” some users asked for clarification on the concept of the “exceptional scenario” to which “Superphiz.eth” referred. However, he ignored them.
The Ecosystem Development Fund explained that the failure occurred because of the high load on individual customers at the consensus level.. But they don’t know what caused it.
The problem with transaction processing is just another reminder that Beacon Chain is still being refined.
Although such a quick response from developers indicates thorough preparation and a high level of professionalism, according to analyst Arnold Toh.
The developers’ prompt response indicates a thorough preparation and a high level of professionalism.