Restaking Risks with
summary
Explains concrete models and failure modes for EigenLayer: contrasts pooled vs attributable security (pooled smudges coverage across 100+ AVSs, attributable buys slashing rights so one AVS can claim ~$3B of protection), details the slashing veto committee and its short‑term gatekeeping, shows how LRT looping and external lending create leveraged restaking and cascade risk, and flags operational limits like withdrawal delays that let LRTs depeg and trigger rapid liquidity crunches.
AI-written summary · about
chapters (23)
- 0:00Intro: Breaking down risks in EigenLayer
- 0:54What is restaking and AVS explained
- 3:13Real-world examples of AVSs and use cases
- 4:49Operators, stakers, and service builders
- 5:51What are liquid restaking tokens (LRTs)?
- 7:32Can LRTs be restaked or looped?
- 8:42Importance of full risk accounting
- 9:50Pooled security vs. attributable security
- 11:31Buying and assigning slashing rights
- 13:33Market dynamics for AVS security
- 14:46How AVSs incentivize stakers
- 16:29Token rewards and APR boosting
- 18:07What happens when AVSs go wrong
- 19:42Slashing governance and veto committees
- 21:12Future of permissionless AVS onboarding
- 22:15Risks of collusion and slashing protection
- 23:18System impact from major AVS slashing
- 24:25IgenLayer’s fail-safes and withdrawal delays
- 25:58Leveraged restaking risks explained
- 27:39Cascade effects and LRT depegging
- 28:39Stablecoins or CDPs built on LRTs
- 29:49Can the EigenLayer token collateralize the system?
- 30:23Other scenarios leading to mass slashing
related talks
31mThe Restaking War
16mDiscussion - Security 2, Session 9
20mRisk Methodology: Introduction for Tokenised Assets in DeFi
33mFireside Chat
13mUncharted Territory Ahead: Why Restaking Needs Modularity
21mThe Credit Layer Vaults, Lending Markets, and the Next Phase of DeFi
22mRisk Management Approach to Security
11mRisk isolation - Building Single Purpose Protocols