The Butterfly Effect
summary
Small coding oversights cascade into major losses: a single '>' vs '>=' bug in Compound’s liquidity‑mining accounting mints roughly $80M extra rewards, and an uninitialized contract plus delegatecall self‑destruct logic sits live for 18 months before discovery. The remedy focuses on process not luck: strict 100% coverage on critical paths, clear coding standards, explicit failure paths and invariants, test‑driven development, and upgrade plans that account for governance delays so bugs get caught before deployment.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:34Smart contracts as mission critical software
- 4:04A real world example
- 5:41Some interesting cases
- 7:44Compound liquidity mining accounting error
- 9:34Aave incorrect initialization of the protocol contracts
- 12:47What does NASA do?
- 16:15Translating these concepts to smart
related talks
20mSolidity's most common security pitfalls and its best safeguards
25mCommSec D2 - Smart Contract (In)Security
23mThanks for all the bugs!
43mOutsmarting Smart Contracts
33mManaging Risk for Compound
51mA Deal with the Devil: Breaking Smart Contracts
20mLearning How to Build Secure Smart Contracts
49mHacked Blockchain Projects What we’ve learned