Securely Scaling Decentralized Governance
summary
Explains concrete failure modes and defenses: on-chain upgrades can introduce bugs (Compound proposal 62 causes a $147M bug), token voting enables plutocratic or coercive moves (Solend upgrade to seize an account), flash loans let attackers push proposals through (Beanstalk loses $77M via a flash-loan takeover), and short voting windows enable surprise execution. Covers mitigations: longer votes and timelocks, multisig execution, monitoring with Defender/Forta, proposal QA and formal verification, optimistic governance (UMA), and staged revocable delegation with emergency pause guardians.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:18About Me
- 1:07Overview
- 2:21What am I covering?
- 3:04Decentralized Governance What does it mean and how should we classify it?
- 4:45Lifecycle for EIP Upgrades
- 5:22Explicit Governance
- 9:05Lifecycle for Compound Governor Proposals
- 10:11Security of Upgrades
- 12:52Coin Voting Governance
- 15:19Operational Overhead & Accountability
- 16:52Governance Attacks
- 18:38Strategies for Securing DAOS Scaling decentralized governance with a focus on security
- 25:18Educate on Proposal Lifecycles
- 29:16On-chain Governance Scaling Visualized
- 30:43Compound DAO Governance Visualized
- 31:29Zcash Governance Visualized
- 32:35Going Forward
related talks
23mSecurely Scaling Decentralized Governance
16mSmart Contract Governance
20mDiscussion - Security, Session 8
22mGrowing & Securing Networks What’s Next for Onchain Governance
26mFireside Chat
27mGovernance and Security Concerns
16mExploring Attacks in the Modular Rollup World
16mA Future to Protocol Upgradability