Discussion - Protocols, Session 1
summary
Explains using create2 deterministic address to preauthorize a fix without publishing code, warns proof of stake only detects censorship of forks not single-proposer omission so slashing may be ineffective, shows simulations on the Uniswap V3 East USDC pool that make TWAP manipulation cost absurdly high but dependent on liquidity shape, describes the tradeoffs of a median TWAP trade-offs versus mean and recommends smaller windows, and advocates Foundry test-driven development plus tighter governance norms and automated integration tests.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:27Slashing mechanisms
- 3:15Security vs safety
- 5:12Price manipulation on Uniswap
- 7:40Coordinating decentralized teams
- 13:02Governance participation
- 15:13Test-driven smart contracts
- 17:42Spec to test to code
- 18:47Mission-critical smart contracts
- 21:54Security culture maintenance
- 23:41Decentralized onboarding
- 25:45Closing and Q&A
related talks
11mRisk isolation - Building Single Purpose Protocols
39mThe challenges of building, scaling and securing DeFi protocols
16mA Future to Protocol Upgradability
41mSecurely Scaling Decentralized Governance
03mWorkshop
26mFireside Chat
01h 33mWhite Hat Panel: DeFi Exploits
31mPanel 2: Hard things we forget to talk about