Ethereum experienced a second completion delay on May 12, the developers said.
Terence.eth (@terencechain) wrote in Twitter:
“Mainnet is not ending again. Prysm will release a patch today. We’ll keep you posted!”
Subsequent feedback from Terence.eth indicates that those transactions have now been finalized and that other customers are also releasing patches. However, he said that Ethereum is “not out of the woods,” implying that the issue has not been fully resolved.
This represents the second definitive delay in 24 hours. Ethereum was also unable to complete transactions for 25 minutes on May 11 for reasons that were unclear at the time.
The cause of the problem has now been partially identified. terence.eth said that Ethereum nodes running the Prysm client received problematic certifications that led to the client using increased CPU and memory, leading to a “death spiral.” He said that most clients, except for the Lighthouse client, are prone to similar issues.
Terence.eth also said that Prysm nodes found a “subtle bug” that occurs when clients enter the “death spiral.” This does not seem to be the ultimate cause of the problem.
Superphiz, who commented on yesterday’s delay, said that expect a third incident to occur. He urged node operators to upgrade their hardware and switch to a minority customer.
None of the incidents involved a complete outage of Ethereum. The blockchain continued to partially process the transactions, which were then completed successfully.
The Ethereum post experienced a second delay in completion, but has since picked up and appeared first on CryptoSlate.
