Secure by Design
summary
Compound V3 launches and packages each market into a single contract to improve capital and gas efficiency, replacing V2’s hub-and-spoke. Design follows four stages: spec → code → test → ship, with a non-negotiable assets = liabilities invariant and a mandate of 100% unit test coverage. Monte Carlo simulations shape liquidation rules, a scenario framework runs tests on forks across four chains, and network-specific deployment scripts plus timelocked governance handle upgrades.
AI-written summary · about
chapters (17)
- 0:00Compound Labs approach
- 1:04Compound V2 and V3 overview
- 2:09Shipping blockchain code challenges
- 3:12Specification process importance
- 4:37Compound V3 design attributes
- 6:03Protocol design decision-making
- 7:08Liquidation mechanism simulations
- 8:11Spec as design document
- 9:13Coding as spec compilation
- 10:15Unit testing workflow
- 11:00Focusing on invariants
- 13:24Proving and testing invariants
- 14:49Testing property scenarios
- 16:11Code review importance
- 17:14V3 deployment strategies
- 18:16Protocol evolution planning
- 18:58Q&A
related talks
24m500 days of Security Summer
15mShared Security, Coordinating the Chaos
21mThe Credit Layer Vaults, Lending Markets, and the Next Phase of DeFi
11mSecurity Lifecyle for DAO Proposals
18mLet Devs Be Devs Without Sacrificing Security
33mManaging Risk for Compound
16mDesigning Holistic Security Programs
11mRisk isolation - Building Single Purpose Protocols