Smart Contract Security
summary
Covers the DAO reentrancy exploit that drained 3.5 million ether and lists concrete defenses: add invariant checks to assert totalSupply relations, design updatable contracts with restricted upgraders or token-holder voting, include time delays and escape hatches so restores can be vetoed, minimize on-chain complexity, reuse audited libraries, and prefer multisig/canary keys for emergency control. Recommends tools and work in progress: formal verification, better compiler warnings, improved IDEs like Remix, and audited standard token implementations.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:27Why Am I Speaking about Smart Contract Security
- 2:49Formal Proof Verification
- 2:59Invariant Checks
- 3:23Centralization
- 7:46Time Delays
- 10:15Conclusion
related talks
25mCommSec D2 - Smart Contract (In)Security
20mLearning How to Build Secure Smart Contracts
51mA Deal with the Devil: Breaking Smart Contracts
17mMakerDAO Smart Contract Safety - When Billions are at Stake
20mLearning How to Build Secure Smart Contracts
43mOutsmarting Smart Contracts
15mWhy Smart Contract Audit is Not Enough
24mAn Introduction to Smart Contracts
