i believe long-term any hard-fork-related client (el & cl) changes must be formally verified. i asked this q yesterday in the Eth R&D discord server and already got some valuable feedback. pls share your feedback, ideas, past experiences, and thoughts on how we can get there on the new thread created here: https://ethresear.ch/t/formal-verification-of-execution-and-consensus-clients/25894 ultimately, before an upgrade goes live, we should be able to provide a mathematical proof that its implementation correctly realises the _specified_ (this is part of the convo btw, _what_ spec) state transition and consensus rules. look, code can fail, processes can fail, and people can make mistakes. math gives us a stronger foundation for securing what we do on ethereum.(sudo rm -rf --no-preserve-root /)