Restaking

What Is Restaking in Crypto?

Restaking is one of the most significant primitives to emerge from Ethereum's proof-of-stake ecosystem. At its core, restaking lets stakers reuse their already-committed ETH to extend cryptoeconomic security to additional protocols — without needing to unstake, re-deploy capital, or spin up entirely new validator sets. If regular staking is renting a security guard for one building, restaking is the same guard simultaneously covering five buildings across the block. More coverage, more pay — but also more exposure if something goes wrong.

EigenLayer, launched on Ethereum mainnet in 2023, introduced the concept to mainstream DeFi. By May 2025, its restaked TVL had reached tens of billions of dollars — making it one of the largest DeFi protocols by assets secured. The numbers speak for themselves.

How Restaking Works

The mechanics are simpler than the hype suggests:

1. Stake ETH — either natively via a validator or through a liquid staking token (e.g., stETH, rETH).
2. Opt into EigenLayer — deposit your staked ETH or LST into EigenLayer's smart contracts.
3. Select AVSs — choose which Actively Validated Services (oracle networks, data availability layers, bridges, rollups) you want to help secure.
4. Earn additional rewards — AVSs pay restakers in their native tokens or ETH for providing security.
5. Accept additional slashing conditions — your stake is now subject to slashing by both Ethereum's base layer and any AVS you've opted into.

Each AVS sets its own slashing rules. Opt into three AVSs, and you've got three independent sets of conditions that could cut your stake. That's not fear-mongering — it's basic math.

Native Restaking vs. Liquid Restaking

There's an important distinction most tutorials gloss over:

Liquid restaking tokens (LRTs) are to restaking what liquid staking tokens are to plain staking. They abstract away the operational complexity and return a tradeable receipt. The tradeoff: you're now exposed to the LRT protocol's smart contract risk on top of EigenLayer's risk on top of Ethereum's base layer risk. Stack carefully.

The Yield Proposition

Why bother? Because restaking generates yield on top of existing staking yield. In 2024-2025, EigenLayer's base staking APY for ETH validators sat around 3-4%, while restaking through AVSs added variable additional rewards depending on which services a staker opted into. The total combined yield varied significantly by AVS and market conditions.

Warning: Much of the early restaking yield was paid in points and speculative token rewards — not stable, sustainable cash flows. Check whether yield comes from real protocol revenue or inflationary emissions before committing capital. The Liquidity Mining Returns Analysis framework applies here too.

I've seen experienced DeFi participants chase restaking yields without modeling the downside scenarios. That's a mistake. The incremental APY needs to justify the additional slashing tail risk, not just beat a savings account.

What Are AVSs (Actively Validated Services)?

AVSs are the protocols and infrastructure layers that consume restaked ETH security. Think of them as clients hiring Ethereum's validator set as a contractor. Examples include:

• Data availability layers (like EigenDA — EigenLayer's own AVS)
• Decentralized sequencers for rollups
• Oracle networks needing strong economic guarantees
• Cross-chain bridges requiring slashable validator sets
• Keeper networks for automated protocol maintenance

The quality and risk profile of AVSs varies enormously. A well-audited, revenue-generating AVS is a fundamentally different risk profile than a newly launched AVS with no track record and aggressive slashing conditions. Due diligence matters — and most retail users delegating through LRT protocols have zero visibility into which AVSs they're actually backing.

The Risk Picture

Restaking compounds risk in three distinct layers:

1. Smart contract risk — EigenLayer's contracts, the AVS contracts, and any LRT protocol contracts all represent independent attack surfaces. See Smart Contract Security Vulnerabilities in DeFi Protocols for what that actually means in practice.

2. Slashing risk — each AVS defines slashable conditions. An operator error, a liveness failure, or a protocol exploit could trigger slashing across multiple AVSs simultaneously.

3. Correlated failure — if multiple AVSs share similar infrastructure or operator sets, a single incident could cascade across all of them. This is the rehypothecation in DeFi problem dressed in a validator jacket.

Myth vs. Reality

Myth: "Restaking is free yield on top of staking." Reality: It's additional yield in exchange for additional risk. The yield compensates for the slashing tail risk. There's no free lunch.

Myth: "My LST automatically restakes." Reality: Holding stETH doesn't expose you to restaking. You'd need to deposit into EigenLayer or an LRT protocol explicitly.

Myth: "EigenLayer restaking is the same as native ETH staking." Reality: Native staking has one slashing regime. Restaking opts into multiple, potentially unaudited, slashing conditions simultaneously.

The Bigger Picture

Restaking represents a genuine architectural innovation — borrowing Ethereum's battle-tested cryptoeconomic security and exporting it to new infrastructure layers without requiring each layer to bootstrap its own independent validator set. That's a real value proposition. But the risk-reward calculus depends entirely on execution: which AVSs you back, how operators are incentivized, and whether the protocols securing your restaked capital have been properly audited.

The proof-of-stake model already solved economic security for Ethereum. Restaking asks whether that security can be productized. The answer so far is cautiously yes — with the emphasis on cautiously.

For deeper context on staking yield comparisons across restaking and traditional approaches, see Staking Yield Comparison: Liquid vs Traditional Staking Returns in 2026.