Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
timbeiko.eth
@tim
Pectra Testnet Update 📣 On Monday, Pectra activated on Holesky. An EL bug caused chain splits, resulting in a minority chain being valid, degrading the network health. Holesky validators must take action ASAP, some Sepolia users must upgrade their client. — Holesky validators: we are coordinating a mass slashing event tomorrow Feb. 28 around 15:00 UTC. You should: 1. Update your node (see screenshot) 2. Sync your node to head (new CL branches will help) 3. Right before slot 3737760, disable slashing protection More info here: https://github.com/ethereum/pm/blob/master/Pectra/holesky-postmortem.md#holesky-coordinated-slashings — Sepolia node operators: the fork will happen as previously scheduled at epoch 222464 (Mar. 5, 7:29 UTC). If you are using Geth, Besu, Nethermind or Lodestar, you must update your client to one of the releases listed here: https://blog.ethereum.org/2025/02/14/pectra-testnet-announcement
2 replies
5 recasts
43 reactions
timbeiko.eth
@tim
Why are we coordinating mass slashings on Holesky? While this strategy could not work on mainnet, the hope is that we can get enough Holesky validators online at once to finalize a block on the correct chain. Validators who had previously attested to the invalid chain will get slashed as a result of doing this. Having a finalized block will allow CLs to more easily find peers on and sync to the valid chain. After the mass slashings, Holesky will go through a long period (2-3 weeks) of non-finality again as the slashed validators are existed and their stake drops to <33% of the overall network stake. Once that happens, the validators who never attested to the invalid chain will finalize the valid minority chain. Again, this is not something we could do if such a situation happened on mainnet. CL client teams are already discussing better ways for users to force nodes onto a minority chain in the future. Expect a deeper discussion on the topic on next week's ACDC.
1 reply
0 recast
24 reactions
Aka1748
@5f
111
0 reply
0 recast
0 reaction
