But there was a SSTORE in an admin function that allowed toggling a boolean flag — and that flag was used in another function to compute a jump offset via JUMPI . With a specific storage layout, that flag could point to the dead JUMPDEST .
Dead code is a time bomb. Diffuse it. Title: 0xdeadcode — The Living Dead in Your Bytecode 0xdeadcode
Result: "Dead code" becomes a self-destruct backdoor after a storage collision. But there was a SSTORE in an admin
I recently dissected a contract that had this: Diffuse it
When you compile a Solidity contract, the optimizer doesn't just remove unreachable paths — it buries them. But "unreachable" at compile time is not "unreachable at runtime" if the EVM state can change.
It sounds like you're asking me to develop a post under the handle — likely for a platform like X (Twitter), a blog, GitHub, or a forum such as Ethereum Research or Stack Overflow.