Exploring Restaking: How EigenLayer Enhances Staked ETH for Collaborative Security

Introduction

In September 2022, Ethereum shifted to a proof of stake model, establishing a robust security pool with over 30 million ETH staked by validators who are at risk of slashing for any malicious activities. This pool ensures Ethereum’s safety, yet it remains inactive when it comes to other protocols.

New protocols requiring decentralized validation encounter significant challenges during their initialization phase. For example, oracle networks, data availability layers, and cross-chain bridges demand validators, each of whom requires substantial economic stakes to avert attacks. Building such security from scratch is an expensive endeavor, as every new protocol must attract its own stakers, mint a unique token for staking rewards, and rely on sufficient capital being pledged to guarantee security.

Restaking presents a different model. Instead of creating independent security, new protocols can borrow security from Ethereum. Stakers who have already committed ETH to Ethereum’s consensus can choose to also secure additional services. This enables the same capital to safeguard multiple protocols simultaneously.

EigenLayer has formalized this idea and built the necessary infrastructure. This guide explains how restaking functions, what EigenLayer has brought to the table, and the risks entailed.

How Ethereum Staking Works Before Restaking

To understand restaking, it’s crucial to first grasp its foundation.

Ethereum validators deposit 32 ETH into a staking contract, earning rewards for proposing and validating blocks (currently around 3% to 4% annually). If a validator engages in malicious behavior (such as double-signing or proposing conflicting blocks) or remains offline for extended periods, a portion of their 32 ETH could be slashed.

This mechanism establishes an economic security framework. Attacking Ethereum’s consensus necessitates controlling enough staked ETH such that the penalty for slashing outweighs the potential gains from the attack. With over 30 million ETH staked (around $100 billion at mid-2026 prices), that barrier is extraordinarily high.

Liquid staking protocols like Lido (stETH) and Rocket Pool (rETH) offer an added layer. Users deposit ETH, receive a liquid token reflecting their stake, and can utilize that token in DeFi while continuing to earn staking rewards. Understanding the mechanics of liquid staking tokens and the risks of depegging is vital for comprehending the added risk layer introduced by restaking.

Restaking establishes a secondary layer on top of staking (or liquid staking) where the same ETH securing Ethereum also supports supplementary protocols.

EigenLayer’s Architecture

EigenLayer comprises a set of smart contracts on Ethereum designed to facilitate restaking, allocated for three specific roles:

Restakers. Users who direct their staked ETH (or liquid staking tokens like stETH) to EigenLayer. Restakers contribute to EigenLayer’s contracts and assign their stake to an operator.

Operators. Entities that implement validation software for actively validated services. An operator registers with EigenLayer, receives delegated stakes from restakers, and opts for one or more Actively Validated Services (AVSs). Operators must meet each AVS’s validation standards and may be subject to slashing for non-compliance.

Actively Validated Services (AVSs). Protocols that utilize EigenLayer’s restaked security. An AVS defines its validation logic, reward structure, and slashing conditions. When an operator engages with an AVS, the restaked ETH supporting that operator becomes subject to the AVS’s slashing conditions.

The process unfolds as follows:

1. A restaker deposits stETH (or native ETH) into EigenLayer.
2. The restaker delegates to an operator.
3. The operator opts into AVSs (for instance, EigenDA, a data availability service).
4. The operator runs the AVS’s validation software.
5. The restaker earns additional rewards from the AVS, alongside their standard Ethereum staking yield.
6. If the operator fails to adhere to an AVS’s rules, the delegated stake can be slashed.

EigenLayer’s contracts enforce the delegation and slashing logic, but don’t specify what constitutes a slashing offense. Each AVS creates its slashing contract, which EigenLayer’s DelegationManager invokes during validated slashing events. This modularity allows various protocols to become AVSs, though it also means the security of each AVS’s slashing logic can differ independently.

What Actively Validated Services Look Like

AVSs represent the demand side of the restaking market. They are protocols in need of decentralized validation but prefer not to create their own validator set and token economy from scratch.

The first and largest AVS is EigenDA, a data availability layer developed by the EigenLayer team. Rollups can submit their transaction data to EigenDA instead of Ethereum’s calldata or blobs, minimizing costs while inheriting security from restaked ETH. By mid-2026, EigenDA was processing data for multiple L2 rollups, providing a viable alternative to Celestia and Ethereum’s native blob space.

Other AVS categories include:

Oracle networks. A decentralized oracle may use restaked ETH as its security bond, eliminating the need for oracles to stake a separate token. If an oracle submits inaccurate data, the restaked ETH backing it is subject to slashing. This provides stronger economic assurances compared to a standalone oracle token with a small market cap.

Cross-chain bridges. Bridge validators can be secured using restaked ETH, offering a significant economic deterrent against fraudulent attestations, far more compelling than what a standalone bridge token could present. Given that bridge exploits have cost over $4 billion, the allure of Ethereum-grade security for bridge validation is immense.

Keeper networks. Protocols that require off-chain computation or automation (e.g., liquidation keepers, MEV relayers) can employ restaked security to ensure functionality. An AVS’s slashing contract can penalize operators who fail to act within a specified timeframe.

Coprocessors. Off-chain computation services that produce verifiable outcomes, such as ZK proof generation or AI inference validation, can implement AVS slashing to enforce accuracy. This domain is expanding as more protocols aim to verify off-chain computations without executing them on-chain.

As of mid-2026, EigenLayer had launched over 20 AVSs, with EigenDA managing the largest volume. EigenLayer also expanded to permit any ERC-20 token as a restakable asset, enhancing the potential collateral base beyond ETH and its liquid staking derivatives.

Liquid Restaking Tokens: The Third Layer

Just as liquid staking has created tradable representations of staked ETH (e.g., stETH, rETH), liquid restaking protocols have emerged to establish tokens that signify restaked positions.

The leading liquid restaking protocols include:

Ether.fi (eETH). The largest liquid restaking protocol by total value locked (TVL). Users deposit ETH, and Ether.fi stakes and restakes it through EigenLayer, providing users with eETH for use across DeFi. Ether.fi has outpaced rivals in the liquid staking sector by offering a smooth one-step deposit process along with integration with leading DeFi protocols for composability.

Renzo (ezETH). Streamlining the EigenLayer delegation process. Users deposit ETH or stETH, while Renzo manages operator selection and AVS opt-ins, resulting in users receiving ezETH. Renzo differentiates itself by offering diversified AVS exposure: the protocol spreads delegated stakes across multiple operators and AVSs to mitigate concentration risk.

Puffer (pufETH). Focuses on solo validator engagement and anti-slashing technology alongside liquid restaking. Puffer’s strategy features secure-signer technology designed to prevent validators from creating slashing messages, even if keys are compromised.

Kelp (rsETH). Aggregates restaked positions from various operators and AVSs into a single liquid token. Kelp aspires to deliver diversified restaking exposure similar to an index fund approach.

Liquid restaking tokens (LRTs) increase convenience but also bring an additional layer of smart contract risk. The progression evolves as follows: ETH → staked ETH → liquid staking token → restaked on EigenLayer → liquid restaking token. Each layer introduces its own contracts, governance, and potential points of failure. A bug or exploit at any layer can have cascading consequences.

The Arithmetic of Shared Security

The value proposition of restaking is grounded in straightforward economics.

Imagine a new oracle network requires $100 million in economic security to prevent attacks. Without restaking, it must convince stakers to acquire and lock $100 million worth of its native token. This token needs stability, liquidity, and market trust—characteristics a nascent project typically lacks initially.

With restaking, the oracle network becomes an AVS on EigenLayer. It leverages security from ETH that is already staked, an asset with a strong market and established value. The oracle doesn’t create a staking token but compensates operators in ETH, using the $100 million in restaked ETH to secure those operators.

The AVS’s expenses relate to the rewards it must allocate to operators (and thus restakers) to incentivize participation. This is usually expressed in the AVS’s native token or in ETH. The cost is lower than that of forming an independent staking ecosystem since restakers already earn a base staking yield. The AVS only needs to provide marginal rewards sufficient to justify the added slashing risk.

For restakers, the allure lies in yield stacking. A position may yield:

• 3.5% from Ethereum consensus staking
• 0.5% from liquid staking protocol fees
• 1% to 3% from AVS rewards via restaking

Total yields reaching 5% to 7% on ETH attracted a considerable influx of capital into restaking during 2024 and 2025. At its height, EigenLayer managed over $15 billion in restaked assets, positioning it as one of the largest DeFi protocols by total value locked (TVL).

However, yield stacking is not without its hazards. Each additional percentage of yield corresponds with elevated risk exposure. The greater the total yield, the more slashing vectors the position faces.

Slashing Risk: Where Restaking Becomes Dangerous

The accumulation of yield introduces increasing risk. Restaked ETH can be subject to multiple sources of slashing simultaneously.

Ethereum Consensus Slashing. If the underlying validator commits double-signing or another fault, the base stake is slashed per Ethereum’s guidelines. This risk remains irrespective of whether restaking is involved.

AVS Slashing. Each AVS the operator engages with has its own slashing terms. An operator participating in three AVSs faces three distinct sets of slashing conditions. A bug in any single AVS’s slashing contract could trigger erroneous slashing.

Correlated Slashing. If an operator manages multiple AVSs and a single infrastructure failure (e.g., a data center outage or key compromise) leads to violations across all of them, the same stake may be slashed multiple times. EigenLayer’s contracts allow for proportional slashing, meaning the total penalty could exceed that incurred from any singular AVS.

Smart Contract Risk in Slashing Contracts. The slashing logic for AVSs is defined in smart contracts developed by the AVS team. Any bugs within the slashing contract could penalize honest operators. Unlike Ethereum’s consensus slashing, which has been extensively tested since 2020, AVS slashing contracts are relatively new and less scrutinized.

LRT Compounding Risk. Users holding liquid restaking tokens face all the aforementioned risks, alongside the inherent smart contract risk of the LRT protocol and the possibility of the LRT diverging from its underlying value during slashing events or liquidity problems.

Systemic Risk. If a major slashing incident affects a significant operator, the resulting sell pressure on LRTs may trigger cascading liquidations in DeFi protocols that accept LRTs as collateral. Although a restaking-related liquidation chain reaction hasn’t occurred yet, the structural risk remains as more DeFi protocols incorporate LRTs as collateral types.

The Competitive Landscape Beyond EigenLayer

Restaking is no longer solely an EigenLayer domain.

Symbiotic launched in 2024 as a permissionless restaking protocol. Unlike EigenLayer, which initially supported only ETH and liquid staking tokens, Symbiotic allows any ERC-20 token as collateral, enabling protocols to restake their governance tokens or stablecoins. Its architecture is also more modular: components for slashing terms, reward distribution, and operator management are segmented into distinct contracts that each AVS can tailor independently.

Karak pioneered the notion of multichain restaking, supporting not just the Ethereum mainnet but also restaking on L2s like Arbitrum and Mantle. Karak’s method appeals to AVSs seeking security from assets outside of Ethereum and to restakers who prefer not to bridge to Ethereum mainnet.

Babylon employs the restaking principle with Bitcoin. BTC holders immobilize their Bitcoin in a time-sensitive script, utilizing it to bolster proof-of-stake chains without departing from the Bitcoin blockchain (no wrapping or bridging necessary). Slashing is enforced via a cryptographic penalty method called extractable one-time signatures, revealing the private key of any staker who signs conflicting messages.

The rise of multiple competitors signifies that restaking is maturing into a broader category rather than being limited to a single product. A pivotal long-term question is whether this security fragmentation across competing restaking layers might weaken the unified security model that originally rendered restaking so advantageous. If the same capital is allocated across EigenLayer, Symbiotic, and Karak, the security offered by any individual protocol could be diminished.

How Operator Selection Shapes Risk

Not all operators on EigenLayer have the same risk profile. The choice of operator will determine which AVSs your stake is exposed to, along with the reliability of the infrastructure backing those AVSs and the operational experience of the team managing the node.

Professional operators (such as Figment, P2P, Kiln, and other institutional staking providers) usually maintain redundant infrastructure across multiple data centers, have dedicated security teams, and limit the number of AVSs they join. Solo operators or smaller teams might offer higher yields by enrolling in more AVSs but centralize risk among fewer hands and less resilient infrastructure.

Operator track records serve as the most reliable indicators. EigenLayer’s delegation dashboard displays historical uptime, any slashing incidents, and the list of current AVS commitments. An operator with 99.9% uptime over 12 months and a careful AVS selection represents a significantly different risk profile compared to a new operator pursuing aggressive multi-AVS strategies.

Delegation is not permanent. Restakers can choose to re-delegate to different operators, though this process includes a withdrawal delay. If an operator begins to engage with AVSs that have unclear slashing conditions or lack thorough audit histories, re-delegation becomes the primary risk management strategy for restakers.

What This Does Not Cover

This guide clarifies restaking mechanics and risks but does not encompass:

• A detailed comparison of individual AVSs and their reward structures
• The tokenomics of the EIGEN token and its governance roles
• Step-by-step instructions for restaking via specific protocols
• The regulatory classification of restaking yields

Practical Checks Before Restaking

Understand Operator Risk. When delegating to an operator, you assume their slashing risks. Investigate which AVSs the operator has opted into, their uptime history, and their infrastructure setups. An operator managing 15 AVSs on a single server in one data center represents concentrated risk.

Review AVS Slashing Conditions. Before your operator joins a new AVS, understand what triggers slashing. Some AVS slashing conditions are clear-cut (e.g., failing to submit data promptly), while others can be complex or reliant on dispute resolution mechanisms that lack stress-testing.

Assess LRT Risks Separately. If you hold a liquid restaking token, recognize that you are responsible for both restaking risks and the smart contract risks associated with the LRT protocol. Review audit reports for both the LRT protocol and the underlying restaking contracts. Evaluate the LRT’s redemption mechanism: some LRTs allow instant redemption, while others may require queued withdrawals.

Monitor Your Position. Restaking should not be perceived as a deposit-and-forget strategy. New AVSs, changes in operators, and slashing incidents can alter your risk profile. Protocols such as EigenLayer offer dashboards that reveal operator performance and AVS status. Consider setting notifications for operator changes if the protocol permits.

Consider the Withdrawal Queue. Restaked positions can have lengthier withdrawal periods than standard staking. EigenLayer imposes a withdrawal delay (currently set at 7 days), and during peak demand, the queue may extend further. Avoid restaking funds you may need access to urgently. Factor withdrawal timing into your liquidity planning.