Yorick (yorick)

@justindrake “Five CL teams” - cold 🤣. Grandine is #6; Lambda Elixir maybe eventually #7

• 0 replies
• 0 recasts
• 0 reactions

@vitalik.eth Worst case scenario for Prysm and Lighthouse is a little heavier - they could “strand” their validators in a very specific scenario. Potuz explains this here, it happened on Goerli with Prysm: https://twitter.com/potuz_eth/status/1768418899111113125?t=iFkj6z-YnD1n3GzlyGertA&s=19 Ideally we have no CL > 1/3rd and no EL > 2/3rd.

• 0 replies
• 0 recasts
• 0 reactions

Really heartening to see a team that tackles tech debt instead of carrying legacy code forever because new features >>> code maintenance https://github.com/ethereum/go-ethereum/pull/29169

• 0 replies
• 0 recasts
• 0 reactions

Lighthouse fixes a high CPU corner case when there are both many exits and missed blocks; and Prysm fixes an issue interacting with block building relays, such as the ones accessed through the MEV-boost sidecar. The wisdom of a multi-client network is once more shown. Even a block production bug has small impact.

• 0 replies
• 0 recasts
• 0 reactions

CLWP reports 100% success rate. All 2133 validators were changed to the address of their rightful owners. If even just 10% of these were actually compromised, that’s a lot of ETH that was rescued. Outstanding job!

• 0 replies
• 0 recasts
• 0 reactions

PSA if you were in the CLWP cohort: Exit your validator and make a fresh one on a fresh, secure mnemonic. The attacker with your compromised mnemonic can slash you, and if they are savvy, get paid for it by the protocol.

• 0 replies
• 0 recasts
• 0 reactions

Shapella went well. Execution changes and withdrawals are being processed, and of course exits work as before. CLWP did good work to help protect people whose mnemonic was compromised. They seem to have been largely successful. Two hot fixes out that users may want: Lighthouse and Prysm.

• 1 reply
• 0 recasts
• 0 reactions