0xdeadcode Review

I recently dissected a contract that had this:

Then I traced the JUMPDEST that should be unreachable — but a storage collision could reanimate it. 0xdeadcode

function withdraw() external { if (false) { selfdestruct(payable(owner)); } // normal withdrawal logic } The optimizer removed the if (false) branch in bytecode entirely — or so I thought. Actually, the compiler preserved a JUMPDEST but no incoming JUMP opcode. I recently dissected a contract that had this: