Section IV: Restaking

Rollups multiply Ethereum's transaction capacity by moving computation off-chain. Proof-of-stake enabled a different kind of multiplication: the ability to reuse staked capital across multiple protocols simultaneously. This innovation, called restaking, represents a new frontier in capital efficiency with its own set of risks and rewards.

The Core Mechanism

EigenLayer pioneered this approach by creating a system where validators can opt in to secure Actively Validated Services (AVSs). These are external protocols that need the kind of security that comes from having real money at stake. For native restaking, validators point their withdrawal credentials to an EigenPod and delegate to an operator. Alternatively, liquid staking token holders can deposit their tokens into EigenLayer strategies. Either way, participants commit to follow the rules of their chosen AVSs, and breaking those rules means facing additional slashing penalties on top of any Ethereum-level punishments.

Multiple protocols can now tap into Ethereum's massive validator set and the billions of dollars they have at stake. This provides shared security rather than building separate systems from scratch. AVSs cover a wide range of applications: data availability layers like EigenDA, oracle networks that provide price feeds, cross-chain bridges, rollup sequencers, and automated keeper networks that maintain DeFi protocols. Each AVS defines its own slashing conditions, the specific rules validators must follow to avoid penalties. A data availability service might require validators to prove they're storing certain data, while an oracle network might slash validators who submit price feeds that deviate too far from consensus.

Technical Architecture

EigenLayer's design reflects careful consideration of how multiple protocols and validators interact. The architecture separates concerns into distinct layers that enable flexible composition while maintaining clear security boundaries.

Strategy contracts handle deposits and withdrawals for ERC-20-based restaking. When users deposit LSTs or other supported tokens, these strategies track ownership and manage the underlying assets. Each strategy represents a different restaked token: one for stETH, another for cbETH, EIGEN, and so on. Native restaking is tracked separately through EigenPods, contract instances that hold validator withdrawal credentials and account for restaked beacon-chain ETH. This modular split lets EigenLayer support both liquid staking derivatives and native staking without one monolithic contract trying to handle every asset type.

Slashing contracts enforce each AVS's specific rules independently. This separation is crucial: it prevents bugs in one AVS's slashing logic from affecting other services or compromising the core deposit/withdrawal mechanisms. When an AVS needs to slash a misbehaving operator, it interacts only with its own slashing contract, which then coordinates with the core system to execute penalties.

The system enables delegation, allowing users who don't want to run validator infrastructure to stake through professional operators. Delegators retain control over their withdrawal rights and can exit and delegate to a different operator after serving the required withdrawal delay, but they also inherit the operator's performance and slashing risks. Operators can signal their commission rates and which AVSs they support, creating a marketplace where delegators can choose based on expertise, fees, and risk profiles.

Different AVSs employ varying proof systems depending on their security needs. Some rely on fraud proofs that assume honest behavior unless challenged. If someone detects invalid behavior during a challenge window, they can submit evidence that triggers slashing. Others use validity proofs based on zero-knowledge cryptography that mathematically guarantee correctness before any state change occurs. Still others depend on committee signatures from trusted parties, which are faster and simpler but introduce trust assumptions about committee honesty and availability.

EigenLayer's security model includes veto committees as an extra layer for critical slashing decisions. Rather than allowing immediate, automated slashing for all violations, some conditions require committee approval. This prevents hasty or incorrect penalty enforcement. Imagine a bug in an AVS that incorrectly flags honest behavior as malicious. The veto committee can pause the slashing, investigate the issue, and prevent unjust penalties. However, this introduces governance risk and potential delays in enforcing legitimate slashing. The exact veto-committee design and implementation have been evolving alongside the rollout of slashing, so details may change over time.

Perhaps most intriguingly, EigenLayer introduces intersubjective slashing, where some violations can’t be proven purely on-chain and instead rely on shared human judgment (social consensus) to decide when to slash. Consider an oracle AVS where validators should report accurate price data. If a validator reports an obviously wrong price (claiming ETH trades at $1 when all exchanges show $3,000), the violation is clear to humans but hard to prove on-chain without introducing centralized price feeds. Intersubjective slashing allows such cases to be resolved through social consensus and governance processes. Token holders or designated committees vote on whether slashing should occur based on off-chain evidence. This flexibility enables the system to handle complex, real-world scenarios that pure algorithmic approaches might miss, but it introduces governance risks and the potential for contentious decisions that divide the community.

Current Economic Reality

On paper, restaking looks like a clean win: more protocols can "rent" Ethereum's security instead of bootstrapping their own validator sets. In practice, the system is still early and somewhat lopsided. A large amount of ETH and liquid staking tokens has been restaked into EigenLayer and liquid restaking wrappers, but only a subset of AVSs see meaningful real-world demand today. Most of the incremental rewards restakers currently earn come from incentive programs, airdrops, and protocol token emissions rather than durable fee revenue generated by AVSs themselves. For now, restaking behaves less like a mature cash-flow asset class and more like a leveraged bet on the future success of the EigenLayer ecosystem.

This timing mismatch matters significantly. The extra liabilities are live today (additional smart contract risk, governance risk, and correlated slashing exposure across multiple AVSs), while the long-run fee markets that are supposed to compensate restakers are still being designed and battle-tested. When you hear claims about "reusing security" or "unlocking capital efficiency," it's worth remembering that many restakers are currently taking on large tail risks for economics that depend on ongoing incentives and a still-uncertain AVS adoption curve.

The Risk Landscape

Understanding the technical architecture reveals why restaking carries significant risks. The most pressing concern is correlated slashing risk. When validators secure multiple AVSs simultaneously, a single mistake or malicious action can trigger penalties across all services at once, amplifying potential losses far beyond standard Ethereum staking. This makes AVS risk assessment essential, since each service brings its own slashing conditions, upgrade mechanisms, and governance structures that validators must understand and trust.

Choosing the right operator becomes pivotal in this environment. Most restakers delegate their validation duties to professional operators who must maintain infrastructure for multiple protocols at once. Poor operator performance or malicious behavior doesn't just affect one service; it impacts all delegated stake across every AVS that operator supports.

Withdrawal delays can extend well beyond Ethereum's standard unbonding periods. EigenLayer adds its own roughly two-week escrow period (currently about 14–17 days depending on the contract version) on top of Beacon Chain exit timing. Individual AVSs or LRT (liquid restaking token) protocols may impose additional withdrawal restrictions on top of this.

The liquid restaking ecosystem introduces systemic risks that compound on top of the liquid staking risks discussed earlier. Liquidity cascades could emerge if LRT tokens lose their peg to underlying ETH, potentially forcing mass withdrawals that create destructive feedback loops across the entire restaking ecosystem. There's also basis risk between the underlying ETH staking yields and LRT token prices, adding complexity for users who expect predictable returns. When you layer restaking on top of liquid staking protocols like Lido or Rocket Pool, you're compounding multiple layers of smart contract risk, economic assumptions, and potential failure points.