🔄 EigenLayer Internals

How EigenLayer works in 90 seconds

EigenLayer lets an Ethereum validator's 32 ETH stake (or an LST share of it) do double duty — first securing consensus, then re-pledging the same economic weight to additional services. A restaker follows one of two paths. The native-restaking path deploys an EigenPod contract and repoints a validator's withdrawal credentials at it, so the validator's principal and rewards accrue inside the pod. The LST path deposits whitelisted tokens like stETH, rETH, and cbETH into the StrategyManager, which assigns them to per-asset Strategy contracts and mints accounting shares.

Once a user holds restaked shares they delegate them to an operator via the DelegationManager. Operators then opt into individual Actively Validated Services through the AVSDirectory; today the flagship AVSs include EigenDA for data availability, AltLayer for restaked rollup sequencing, Omni Network for cross-rollup messaging, Lagrange for ZK coprocessing, Brevis for ZK data attestation, and Witness Chain for DePIN verification. Each AVS's ServiceManager defines what constitutes a fault and how rewards stream back through the RewardsCoordinator.

Withdrawals are intentionally slow. A queueWithdrawal call starts a 7-day escrow during which any attributable fault can still slash the position; completeQueuedWithdrawal then releases principal and accrued AVS rewards. For native restakers the ETH also has to exit the beacon chain's validator queue, which can add another week when the exit queue is busy. The combined delay is what allows EigenLayer's social-consensus layer and the Security Council's veto committee to respond to a malicious AVS or a buggy slashing rule before funds physically move.

Key concepts

EigenPod (native restaking)

An EigenPod is a user-deployed contract that owns a validator's withdrawal credentials. Beacon-chain rewards land in the pod, and the pod's balance is what counts toward EigenLayer's native restaked stake. Each pod is one-to-one with a set of validators a single staker runs, so native restaking scales with validators-under-management rather than with LST liquidity.

Strategies and the StrategyManager

LST restaking routes every whitelisted token through a dedicated Strategy contract — one for stETH, one for rETH, one for cbETH, and so on. The StrategyManager tracks each staker's share balance, applies the restaking APR to reward accounting, and gates deposits by per-strategy caps that EigenLayer governance adjusts as demand shifts between LSTs.

AVS (Actively Validated Service)

An AVS is an application that pays operators to perform off-chain work and slashes them for misbehaving. The AVS registers its ServiceManager, StakeRegistry, and BLSApkRegistry in the AVSDirectory, defines which strategies it accepts as collateral, and signs the opt-in digest operators submit. EigenDA, AltLayer, Omni, Lagrange, Brevis, and Witness Chain are the flagship production AVSs as of April 2026.

Operator registration and AVS opt-in

Operators call registerAsOperator on the DelegationManager, publish service metadata, and set commission. Stakers delegate by calling delegateTo. The operator then opts into each AVS individually via registerOperatorToAVS, which means the operator's slashable surface is the union of every AVS it has signed into — not every restaked wallet it serves.

Slashing and the veto window

Slashing fires only on on-chain attributable faults — double signing, invalid state roots, missed duty windows — not on subjective complaints. A fraud-proof window precedes burns, during which the EigenLayer Security Council can veto a malformed slash. The design tradeoff is capital efficiency versus cascade risk: the same stake backs multiple AVSs, so a correctly triggered slash on one service reduces the collateral securing every other AVS an operator runs.

Withdrawal escrow

queueWithdrawal on the DelegationManager starts a 7-day escrow designed to keep stake slashable during the window where a fraud proof could still land. Only after the escrow completes can completeQueuedWithdrawal pay out principal plus AVS rewards, and native restakers additionally wait for the validator exit queue — so practical time-to-cash typically runs 7–14 days.

Why EigenLayer matters

As of April 2026, EigenLayer is the single largest consumer of Ethereum economic security outside Ethereum itself, coordinating tens of billions of restaked ETH across native pods and LST strategies. By giving AVSs a way to rent a slashable security budget instead of bootstrapping their own validator set with a new token, EigenLayer collapses the cost curve for launching shared-security services — data availability, coprocessors, bridges, and decentralized sequencers that would otherwise need a multi-year token-distribution campaign.

The tradeoff the protocol is being stress-tested on is correlated risk. Because one operator can secure EigenDA, AltLayer, Omni, Lagrange, and Witness Chain on the same 32-ETH native restake, a single operator bug now threatens every AVS that operator serves. EigenLayer's mitigation is a slow slashing rollout, per-AVS caps on penalty weights, and the Security Council veto. Restaked APRs of 5–8% — roughly the 3.2–3.5% base ETH yield plus 1–3% per mature AVS — are the market-clearing compensation for that expanded risk surface.

Frequently asked questions

What is the difference between native restaking and LST restaking on EigenLayer?

Native restaking requires pointing a 32-ETH validator's withdrawal credentials at an EigenPod contract the user deploys; the validator's principal and rewards are locked inside the pod and counted as native restaked stake. LST restaking instead takes stETH, rETH, cbETH, or other whitelisted liquid-staking tokens into the StrategyManager, each of which lives in its own Strategy contract. Native restaking caps at the user's validator count while LST restaking scales with whichever LSTs EigenLayer governance has approved.

What does an AVS actually do?

An Actively Validated Service registers in the AVSDirectory and defines its own StakeRegistry, BLSApkRegistry, and slashing conditions. Operators who opt into the AVS run its off-chain software — a data-availability committee for EigenDA, a cross-rollup messaging node for Omni Network, a ZK coprocessor for Lagrange, a bridge watcher for Witness Chain — and the AVS contract pays rewards to the operator set or slashes them according to its on-chain quorum rules.

How does operator registration and opt-in work?

An operator calls registerAsOperator on the DelegationManager, publishes a signed service URL, and optionally sets a commission rate. Stakers delegate their restaked shares to that operator. The operator then opts into individual AVSs by calling registerOperatorToAVS, signing an AVS-specific message that the AVS's ServiceManager verifies. The opt-in is explicit and per-AVS, so an operator can be securing EigenDA without ever touching AltLayer or Omni.

What are the slashing conditions?

Slashing is triggered on-chain by objective, attributable faults — double-signing a message, submitting an invalid state root, or missing a duty window the AVS has codified. A fraud-proof window precedes any burn, during which the EigenLayer Security Council's veto committee can cancel slashes that look erroneous. Because one operator can secure multiple AVSs on the same stake, a slash cascades: if an operator is burned on EigenDA it affects all delegators delegated to that operator, regardless of which other AVSs they cared about.

How do restaking rewards stack on top of base ETH yield?

A restaker keeps the base consensus-layer yield of roughly 3.2–3.5% from the underlying validator or LST, then adds AVS rewards. As of April 2026 a typical mature AVS pays 1–3% incremental APR and an operator running four or five AVSs delivers a blended 5–8% restaked APR after fees. Rewards are distributed through the RewardsCoordinator contract rather than paid directly, and they are earmarked strategy-by-strategy so stakers see which AVS produced which share of the yield.

What happens when I want to withdraw restaked ETH?

Restakers call queueWithdrawal on the DelegationManager, which starts a 7-day escrow. During that window any still-attributable fault on the operator can slash the withdrawal; once the window elapses completeQueuedWithdrawal pays out principal plus accrued rewards. For native restakers the ETH must also be exited from the validator set via the EigenPod, so total time-to-cash can stretch past two weeks if the Ethereum exit queue is congested.

Isn't stacking slashing risk dangerous for Ethereum itself?

EigenLayer caps what a restaker can lose at the value of their restaked position, but correlated slashing across many AVSs is the new risk surface. As of April 2026 the protocol has rolled out slashing gradually — new AVSs launch with capped penalty weights and a 7-day veto window — so a single bug cannot instantly burn a large share of the restaked base, but researchers still track how AVS quorum designs avoid social-consensus-eroding cascades.

Related reading

• Restaking explained — walk through the EigenPod and StrategyManager paths and see exactly how native and LST restaked stake accumulate shares.
• AVSs and operators — look at each flagship AVS (EigenDA, AltLayer, Omni, Lagrange, Brevis, Witness Chain) and how operator opt-in and reward distribution wire them together.
• Slashing conditions — trace a fault from detection through the fraud-proof window, the Security Council veto, and the final slash accounting.
• Symbiotic restaking — contrast EigenLayer's ETH-centric integrated model against Symbiotic's permissionless, vault-centric three-layer architecture.
• Liquid restaking tokens — see how Etherfi, Renzo, and Kelp wrap EigenLayer positions into liquid LRTs that circulate through the rest of DeFi.