0xdeadcode ((link)) — Updated & Latest

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

April 13, 2026

(thread-style) 2. A short blog/forum post exploring a "dead code" vulnerability in smart contracts 1. X (Twitter) Post by @0xdeadcode Main post: 0xdeadcode 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. Then I traced the JUMPDEST that should be