Introduction

EigenLayer represents one of the most significant middleware innovations on Ethereum since the Merge. By enabling the reuse of staked ETH security across multiple decentralized services simultaneously, it introduces a shared security marketplace that fundamentally changes the economics of building trust-minimized infrastructure. This guide assumes familiarity with Ethereum's proof-of-stake consensus, validator operations, and DeFi primitives.

Core Architecture

EigenLayer sits as a set of smart contracts on Ethereum mainnet that allow ETH stakers to opt in to additional validation responsibilities—called Actively Validated Services (AVSs)—in exchange for supplementary yield. The key architectural components:

  • StrategyManager: Handles deposits for LST-based restaking. Each supported token (stETH, rETH, cbETH, etc.) maps to a Strategy contract that tracks shares.
  • EigenPodManager: Manages native restaking. Each restaker deploys an EigenPod—a contract that serves as the withdrawal credential for one or more Ethereum validators.
  • DelegationManager: Handles the relationship between restakers and operators, who run AVS node software on restakers' behalf.
  • Slasher: The contract layer that enforces AVS-specific slashing conditions (progressively being activated through 2024-2025).
  • AVSDirectory: Registry where AVSs register and operators opt in to specific service commitments.

Restaking Modalities

Native Restaking

Native restaking involves pointing an Ethereum validator's withdrawal credentials to an EigenPod contract (0x01-prefixed credentials). The flow:

1. Deploy an EigenPod via EigenPodManager.createPod().

2. Set the pod address as your validator's withdrawal credential.

3. Call EigenPod.verifyWithdrawalCredentials() with a Beacon Chain state proof to activate restaking.

4. The pod verifies inclusion of the validator's balance against the Beacon Block Root oracle (EIP-4788).

This approach carries the full 32 ETH (or more with 0x02 credentials post-Pectra) and exposes the entire validator balance to AVS slashing conditions.

LST Restaking

Liquid staking tokens—stETH, rETH, swETH, etc.—can be deposited into EigenLayer's StrategyManager. This is simpler operationally:

1. Approve the token to the StrategyManager.

2. Call depositIntoStrategy() specifying the relevant strategy.

3. Shares are minted proportionally.

LST restaking carries compounded smart contract risk: the LST protocol, EigenLayer contracts, and each AVS's slashing logic.

Liquid Restaking Tokens (LRTs)

Protocols like EtherFi (eETH/weETH), Renzo (ezETH), Puffer (pufETH), and KelpDAO (rsETH) wrap EigenLayer positions into transferable tokens. These add a fourth risk layer but unlock DeFi composability—LRTs can be used as collateral in lending markets, LP positions, and yield strategies.

Delegation and Operator Mechanics

Restakers delegate their stake to operators who register on-chain via DelegationManager.registerAsOperator(). Key details:

  • Delegation is all-or-nothing per restaker address: you cannot split delegation across multiple operators from the same address.

  • Operators choose which AVSs to opt into. Each AVS has its own registration contract and may impose minimum stake thresholds.
  • Operators run off-chain node software specific to each AVS (e.g., EigenDA's disperser nodes, Omni Network's cross-chain relayers, AltLayer's sequencer sets).
  • Operator commission rates are set at registration and define the yield split between operator and delegators.

Slashing: The Critical Risk Layer

Slashing is the mechanism that gives restaked security its economic meaning. As of early 2025, EigenLayer has been progressively activating slashing through its ELIP-002 slashing upgrade:

  • Each AVS defines slashing conditions in a contract implementing the ISlasher interface.
  • If an operator provably violates AVS rules, a designated slashing oracle or dispute resolution system can trigger Slasher.slashOperator().
  • Slashed amounts are burned or redirected per AVS configuration.
  • Veto committees provide a human-layer safety check—a multisig or governance process that can block illegitimate slashing requests within a challenge window.

Edge Cases and Risk Vectors

  • Cascading slashing: An operator opted into five AVSs could be slashed by multiple simultaneously. The restaker's entire position is the collateral base for all, meaning correlated failures can wipe out more than expected.
  • Attributable vs. non-attributable faults: Some AVSs can cryptographically prove misbehavior (double-signing). Others rely on subjective dispute games, introducing trust assumptions.
  • Withdrawal delays: Unstaking from EigenLayer involves a 7-day withdrawal delay (escrow period) during which slashing can still apply. This prevents slash-and-run attacks but locks liquidity.
  • LST depeg + slashing compounding: If the underlying LST depegs while an AVS slashing event occurs, the effective loss to the restaker is multiplicative.
  • Operator key management: Operators typically maintain separate ECDSA and BLS keys per AVS. Compromise of these keys can lead to attributable faults and slashing even without malicious intent.

AVS Ecosystem Snapshot (2025)

Notable AVSs leveraging EigenLayer security:

| AVS | Function | Status |

|-----|----------|--------|

| EigenDA | Data availability layer | Mainnet |

| Omni Network | Cross-chain messaging | Mainnet |

| AltLayer | Rollup-as-a-Service infra | Mainnet |

| Brevis | ZK coprocessor | Mainnet |

| Lagrange | State committees/ZK proofs | Mainnet |

| Witness Chain | DePIN coordination | Mainnet |

Each AVS offers different reward tokens and risk profiles. Operators must evaluate the marginal risk per unit of additional yield when opting into new services.

Practical Considerations for Advanced Operators

  • Diversification at the operator level: Run multiple operator addresses if you want to isolate slashing risk across AVS sets.

  • Monitor quorum thresholds: Many AVSs require minimum total stake in specific quorums (ETH quorum vs. LST quorum). Falling below thresholds can affect rewards.
  • Gas costs: Native restaking proof verification (verifyWithdrawalCredentials) requires Merkle proofs against the beacon state root—these transactions can cost 200k-500k gas.
  • Pectra implications: The Pectra upgrade's 0x02 withdrawal credentials and MAX_EFFECTIVE_BALANCE increase (2048 ETH) changes the calculus for native restaking by allowing consolidated validators.
  • Programmatic monitoring: Use EigenLayer's subgraph and emitted events (OperatorSharesIncreased, StakerDelegated, WithdrawalQueued) to build automated dashboards.

Risk Framework Summary

| Risk | Native Restaking | LST Restaking | LRT Restaking |

|------|-----------------|---------------|---------------|

| Smart contract risk | EigenLayer + AVS | + LST protocol | + LRT protocol |

| Slashing exposure | Full validator balance | Deposited amount | Deposited amount |

| Liquidity risk | 7-day exit + beacon exit | 7-day exit | DEX liquidity dependent |

| Depeg risk | None | LST depeg | LRT + LST depeg |

Conclusion

EigenLayer transforms ETH from a single-purpose consensus asset into a programmable trust substrate. For advanced participants, the opportunity is substantial—but so is the complexity. Understanding the precise slashing mechanics, withdrawal timing, and compounded risk layers across AVSs is not optional; it is the prerequisite for responsible participation in the restaking economy. As more AVSs launch and slashing goes fully live, the spread between restaking yield and restaking risk will become the defining metric of this ecosystem.