Context Ethereum's Casper FFG finality mechanism is designed so that once a block is finalized, it becomes irreversible — at least without burning at least 1/3 of the total staked ETH. But what if the block that gets finalized is invalid? This is not merely a theoretical curiosity. It sits at the intersection of consensus safety, execution correctness, and social coordination, and the answer is far less clean than "the chain just rolls back." This runbook explores the scenario end-to-end: how it could happen, what the immediate consequences are, what options the community has, and what the trade-offs of each response look like. How Could This Happen? An invalid block reaching finalization requires a cascading failure across multiple layers of defense. No single bug is enough — it takes a combination. Possible contributing factors:
2/23/2026Network Fork Name Time UTC Epoch Start Slot Unix Timestamp Hex Timestamp Fork ID Holesky
10/31/2025ICC Wifi discussion points Networking equipment FortiGate 500E Aruba 6200f 24g class4 poe 4sfp+ 370w switch Aruba 6200f 48g class4 poe 4sfp+ 740w switch Aruba AP-515 Access Points Aruba 7210(RW) Wireless Controller Costs unknown - I'm hopeful that this has no extra cost, as it should be included in the uplink cost. Would be good to confirm.
7/7/2023:::info :mega: 4844 requires a trusted setup file, Please ensure that there is a way for us to specify the file through a runtime flag such as --trusted-setup-file (or similar). If the file is baked in during compile, please ensure that the flag would indeed override the file. This is a MUST requirement for devnet 6. If your client does not support the override, we can't include it in the devnet. ::: :::info :mega: The c-kzg trusted setup file has been updated since devnet 5. Please make sure you use the correct values. This can be found here. ::: Consensus Specs @ Commit 0682b22 aka v1.4.0-alpha.3 :heavy_check_mark:
6/14/2023