Clear as Mud
summary
Argues that compiler/EVM interactions produce real bugs and gives three concrete rules: don't obfuscate — auditors hit a huge caller graph when projects split into tiny files; don't bake upgrade/backdoor paths — examples around the diamond standard backdoors and stolen keys show upgradeability invites compromise; do apply security tooling end-to-end — start with static analysis and formal verification, use mutation testing and audits; stop blanket-applying defensive patterns like nonReentrant where it isn't needed.
AI-written summary · about
chapters (6)
related talks
51mPreventing Security Bugs through Software Design
22mCompilers should get over themselves and respect semantic dependencies!
48mSecurity today: change your habits and make it safer and efficient
41mBattle of the Languages
50mCracking the Code to Secure Software
46mRethinking Architectures and Abstraction for a World Where Security Improvements Matter More than Performance Gains
45mEradicating Vulnerability Classes by Shelving SAST and Embracing Secure Defaults and Invariants
40mPrinciples For Secure & Reliable Systems