Securely Scaling Decentralized Governance
summary
Decentralized governance needs concrete controls: use long voting windows, time locks, delegated operational units, and emergency multisigs rather than vague promises. Examples include Beanstalk $77M attack and token-borrow manipulation, the Compound governor: 2d review, 3d vote, 2d timelock flow, and incident-driven checklist for listing tokens like TrueUSD’s double-entry bug. Implement continuous monitoring (Forta), codified off-chain rules (constitutions), minimize upgradeable surface area, and require proposal QA steps and explicit security signoffs before execution.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:04Decentralized governance
- 2:06Implicit vs explicit models
- 3:51DAO decision structures
- 5:16Governance pain points
- 7:21Protocol upgrade risks
- 8:45Governance attacks examples
- 10:08Secure governance design
- 12:11Malicious governance costs
- 13:16Security processes for DAOs
- 14:38Off-chain consensus rules
- 15:42DevSecOps for governance
- 16:23Safe delegation practices
- 17:26Complexity vs usability
- 18:48Layered governance example
- 19:52Adversarial governance mindset
- 20:34Governance in Ethereum scaling
- 21:35Governance best practices
- 22:18Closing remarks
related talks
41mSecurely Scaling Decentralized Governance
22mGrowing & Securing Networks What’s Next for Onchain Governance
27mGovernance and Security Concerns
22mA Case for Governators
26mFireside Chat
31mPanel 2: Hard things we forget to talk about
21mThe Centralized Risk of DeFi
16mA Future to Protocol Upgradability