EigenLayer introduced restaking to the Ethereum ecosystem in 2023 and, in doing so, created one of the most discussed and least fully understood concepts in blockchain infrastructure. The basic idea is straightforward: ETH that has been staked to secure Ethereum can be simultaneously “restaked” — committed to secure additional protocols or services called Actively Validated Services (AVSs) — in exchange for additional yield. The staker takes on additional slashing risk in exchange for additional rewards. The protocol being secured gets Ethereum’s enormous staked capital behind it without needing to bootstrap its own validator set.
By 2026, the numbers have become meaningful. EigenLayer has accumulated tens of billions of dollars in restaked ETH, making it one of the largest smart contract systems in the Ethereum ecosystem by total value locked. The EIGEN token has been distributed and is trading. The first generation of AVSs — including EigenDA (a data availability service), and several oracle and bridge verification systems — are live and generating restaker rewards.
The concept works mechanically. The question that deserves more honest examination than the restaking community typically provides is what risks have been introduced into the Ethereum security stack, and whether the additional yield adequately compensates for those risks at the current scale of adoption.
How Restaking Works: The Mechanics
Ethereum validators stake 32 ETH to participate in consensus, earning staking rewards (currently around 3 to 4 percent annualised) in exchange for correctly validating transactions and maintaining the network. The staked ETH is subject to slashing — partial confiscation — if the validator behaves dishonestly or negligently (double signing, extended downtime).
Restaking through EigenLayer extends this commitment. A staker (or liquid staking token holder who has deposited stETH or cbETH into EigenLayer) opts into one or more AVSs. Each AVS has its own slashing conditions — specific behaviours that, if detected, result in partial confiscation of the restaked ETH. In exchange for accepting this additional slashing risk, the restaker earns additional rewards in the AVS’s token or in ETH.
The institutional staking yield hierarchy for Ethereum is relevant here. Base staking yields around 3 to 4 percent. Liquid staking through protocols like Lido adds MEV and fee rewards to get yields somewhat higher. Restaking through EigenLayer adds another layer — potentially 1 to 3 percent additional annualised yield depending on which AVSs are opted into and how their reward structures evolve. For institutional holders who are optimising yield on ETH positions, the incremental return is genuinely attractive if the risk is understood.
The liquid restaking tokens (LRTs) — products from EigenLayer partner protocols like EtherFi, Renzo, Puffer, and Kelp — abstract the restaking mechanics into a single token (like weETH from EtherFi) that handles the underlying restaking positions and passes through yields. This makes restaking accessible to users who cannot manage validator operations directly, but also introduces additional smart contract risk: the LRT protocol itself, on top of the underlying EigenLayer smart contracts, on top of the liquid staking protocol (like Lido), on top of Ethereum’s base layer.
The Slashing Complexity and Cascade Risk
The central risk of restaking is slashing complexity. In base Ethereum staking, slashing conditions are well-defined and the result of extensive protocol engineering: a validator is slashed for double signing or for being offline during an extended period. The conditions are binary, the amounts are specified, and the Ethereum protocol handles enforcement. Validators and their operators know exactly what they are signing up for.
AVS slashing conditions are designed by the AVS itself, reviewed by the EigenLayer governance process, and enforced through smart contracts that interact with the restaked ETH. Each AVS adds its own slashing logic on top of the base Ethereum slashing conditions. A restaker who has opted into five AVSs is exposed to five distinct slashing frameworks simultaneously, each with different conditions and each potentially slashing from the same pool of staked ETH.
The compound risk of this arrangement is what some researchers have described as “slashing cascade” — a scenario where an AVS bug, exploit, or governance attack triggers slashing across many restakers simultaneously, which could in theory be large enough to impair the economic security of the underlying Ethereum validator set if the restaked ETH exposure is sufficiently concentrated. EigenLayer has implemented veto committees and slashing review mechanisms to prevent malicious or erroneous slashing, but these are governance mechanisms — human processes — not protocol-level guarantees in the same way Ethereum’s slashing conditions are enforced.
The honest risk assessment: slashing cascade at a scale that materially impairs Ethereum’s security is a tail event, not a base case. The EigenLayer architecture has multiple safeguards. But the tail risk is non-zero and grows as restaked ETH increases as a proportion of total staked ETH. Understanding that the additional yield from restaking compensates for this tail risk is different from understanding what that tail risk actually is.
What AVSs Actually Do and Whether the Demand Is Real
The business case for restaking rests on AVSs — the protocols that use EigenLayer’s shared security. If AVSs generate enough demand and revenue to pay meaningful rewards to restakers, the economic model works. If AVS demand is thin or the rewards are primarily in speculative tokens rather than protocol-generated fees, restaking yield is mostly inflationary token distribution rather than genuine return.
The honest assessment of current AVS economics is mixed. EigenDA — EigenLayer’s own data availability service — is live and attracting some rollup demand, though it competes with Celestia, which launched earlier and has an established ecosystem. Oracle networks, bridge verification services, and decentralised sequencers are the categories of AVS that have attracted most early development interest. These are real infrastructure services with genuine demand, but the fee revenue they generate relative to the restaked capital securing them is currently thin.
Ethereum L2 economics are directly relevant here. If major L2s adopt EigenDA as their data availability layer — in addition to or instead of posting to Ethereum mainnet — that would create meaningful, ongoing fee revenue for restakers. Current adoption has been limited, with most established L2s continuing to use Ethereum mainnet DA or Celestia rather than EigenDA. The AVS revenue case requires adoption growth that has not yet materialised at the scale the restaking TVL implies.
The practical consequence: most restaking yield today comes from EIGEN token emissions — EigenLayer distributing its own token to restakers as part of its growth strategy — rather than from AVS-generated fee revenue. Token emissions are a common and legitimate way to bootstrap network effects, but they create inflationary return dynamics that investors should distinguish from fee-based yield. EIGEN emission yields compress as the token price adjusts for supply and as EigenLayer gradually shifts toward fee-based reward distribution.
The Concentration and Governance Risk
A structural feature of the restaking ecosystem that has received less scrutiny than it deserves is the concentration of restaked ETH in a small number of liquid restaking protocols. EtherFi, Renzo, and a handful of other LRT protocols hold the majority of restaked ETH. This concentration means that decisions made by those protocols’ governance — which AVSs to opt into, how to manage slashing risk, what operator diversification to require — have outsized effects on the aggregate risk profile of restaked Ethereum.
If a liquid restaking protocol makes a poor AVS selection decision and significant slashing occurs, the impact falls on all holders of that LRT — retail investors who may not have closely tracked the underlying AVS exposure. The opacity between a retail user holding weETH or pufETH and the actual slashing conditions of the AVSs that ETH is exposed to is substantial. The yield shows up in the token’s staking rewards; the risk is buried in smart contract relationships that most holders have not read.
EigenLayer has proposed an operator safety score and AVS risk rating system that would help users understand the risk profile of their restaking positions, but as of mid-2026 these tools are still developing rather than fully deployed. The gap between yield visibility and risk visibility is a genuine consumer protection consideration that regulators will eventually examine.
The Long-Term Vision and Whether It Holds
The intellectual case for restaking as a primitive is genuinely interesting. The observation that bootstrapping a validator set for every new blockchain service is inefficient — and that Ethereum already has a large, economically bonded validator set that could be credibly extended to secure other services — identifies a real resource allocation problem. If restaking works as intended, it could become the foundation for a generation of blockchain services that inherit Ethereum’s security rather than replicating it, at substantially lower cost.
The practical execution challenges are significant. Each AVS needs to define its slashing conditions carefully enough to be enforceable without being so broad that they create unexpected slashing events. The AVS business models need to generate sufficient fee revenue to pay restakers competitively, or the restaking economics rely permanently on token emissions that inflate supply. The governance of slashing disputes — currently managed by human veto committees — needs to scale to handle a much larger AVS ecosystem without becoming a single point of failure or capture.
Whether EigenLayer solves these problems in a way that makes restaking a durable infrastructure primitive — comparable to Ethereum’s base staking in terms of reliability and trust — is an open empirical question that the current TVL numbers do not answer. The capital has flowed in response to yield incentives. Whether the underlying infrastructure justifies that capital allocation will be determined by how AVS adoption develops and how the first significant slashing events are handled.
For investors and participants in the restaking ecosystem: the yield is real, the risk is real, and the disclosure is inadequate relative to the complexity of what you are actually opting into. Understanding the mechanism at the level described here — not just the APY on an LRT dashboard — is the minimum required to evaluate whether the risk-reward is appropriate for your position.
