Prysm and Teku Release AnnouncementOn May 11th and 12th, the beaconchain experienced two separate occasions where finality was unable to be reached for 3 and 8 epochs. This appears to have been caused by high load on some of the Consensus Layer clients, which in turn was caused by an exceptional scenario. Although the network was unable to finalize, the network was, as designed, live and end users were able to transact on the network. This was made possible due to client diversity as not all client implementations were affected by this exceptional scenario. After all clients caught up, the network finalized again. For more information on Finality: https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/ The full cause for this is still being evaluated, however, Teku and Prysm have released upgrades that implements optimizations to prevent beacon nodes from high resource usage during these exceptional scenarios. Teku (23.5.0)
Prysm (v4.0.3-hotfix) |
