EigenLayer Primer
TODO: Complete EigenLayer Architecture Overview
This document should introduce readers unfamiliar with EigenLayer to:
Required Sections
-
What is EigenLayer?
- Restaking concept: reusing staked capital across multiple services
- AVLs (Actively Validated Ledgers) vs AVSs (Active Validator Sets)
- EigenLayer as the coordination layer
-
Key Concepts
- Operators: Who runs validators
- Delegators: Who provides capital
- AVSs: Services that use restaked capital
- Slashing: When and why stake is forfeited
-
EigenLayer Architecture
- Core contracts (StrategyManager, DelegationManager, SlasherRegistry)
- Interaction flow: delegator → operator → AVS
- Staking mechanics (deposits, withdrawals, queues)
-
AVS Ecosystem
- Examples of existing AVSs (data feeds, sequencers, threshold cryptography)
- Why operators choose certain AVSs
- AVS competition & market dynamics
-
Risk Considerations
- Multiple concurrent risks from different AVSs
- Operator concentration risk
- Correlation between AVSs
Links & References
- Primary audience: Developers new to EigenLayer
- Prerequisites: Understanding of Ethereum staking
- Related docs:
Status: NOT STARTED — Requires product team expertise on EigenLayer internals