What Is EigenLayer? Ethereum Restaking Explained

EigenLayer is a protocol built on Ethereum that lets staked ETH be "restaked" — reused to provide economic security to additional services beyond Ethereum's own consensus — creating a marketplace where new networks and applications can rent Ethereum-grade security instead of bootstrapping their own validator set and token from zero.

This solves a real, longstanding problem in crypto: launching any new network or service that needs its own decentralized validator set traditionally means convincing enough independent operators to stake a brand-new, unproven token, which is slow, capital-inefficient, and offers relatively weak security in a new network's early days compared to an established chain like Ethereum.

What "restaking" actually means

Ethereum validators lock ETH as a bond, and that ETH is at risk of being "slashed" (partially forfeited) if the validator behaves dishonestly according to Ethereum's own consensus rules. EigenLayer lets that same already-staked ETH (or a liquid staking token representing it) be additionally committed to securing other services, called Actively Validated Services (AVSs) — these might include oracle networks, data availability layers, bridges, or other infrastructure that needs its own honesty guarantees.

By opting in, a validator agrees to additional slashing conditions specific to each AVS they secure, in exchange for additional rewards paid by that AVS. If the validator misbehaves according to the AVS's rules, they can lose a portion of their restaked ETH — separate from (though building on top of) the risk they already carry from standard Ethereum validation.

Why this matters for new networks and services

Instead of a new service having to convince independent capital to stake an unproven, newly created token — with all the cold-start security and liquidity problems that implies — it can instead recruit already-staked ETH validators, who bring Ethereum-level economic security from day one. This is the core value proposition: shared, "rented" security instead of every new service rebuilding its own security budget from scratch.

The risks this introduces

Restaking is not a free lunch — it explicitly introduces new ways for a validator's stake to be slashed, beyond Ethereum's own base-layer rules. Key risks worth understanding:

• Compounded slashing risk. A validator restaking across multiple AVSs takes on each AVS's specific slashing conditions in addition to Ethereum's own — a bug or malicious action tied to any one AVS could result in loss of restaked ETH, even if the validator's behavior on Ethereum's base layer itself was flawless.
• AVS quality variance. Not all AVSs carry the same level of audit rigor, economic design maturity, or operational track record — restaking into a poorly designed or insufficiently vetted AVS carries meaningfully more risk than restaking into a mature, well-audited one.
• Systemic concentration risk. Because restaking pools Ethereum's existing validator security across many services, a severe, cascading failure across a widely-used set of AVSs could, in a worst case, create correlated risk to Ethereum's broader staking ecosystem in ways that didn't exist before restaking was possible — a genuinely new category of systemic risk that the ecosystem is still working through in practice, not just in theory.

Aspect	Standard Ethereum staking	Restaking via EigenLayer
What secures	Ethereum consensus only	Ethereum consensus + opted-in AVSs
Slashing conditions	Ethereum's own rules only	Ethereum's rules + each AVS's own rules
Reward source	Ethereum protocol rewards	Ethereum rewards + AVS-specific rewards
New risk introduced	N/A	AVS-specific bugs/misbehavior; compounded slashing

How liquid restaking fits in

Similar to how liquid staking tokens let stakers access liquidity for otherwise-locked staked ETH (see our liquid staking explainer), a related category of "liquid restaking tokens" has emerged, letting users gain restaking exposure and rewards through a liquid, tradeable token rather than running validator infrastructure or managing AVS opt-ins directly themselves. This adds a further layer of smart contract and operator-trust risk on top of the underlying restaking mechanics — worth evaluating separately from the AVS-level risks described above.

What to check before participating

Given the compounding nature of restaking risk, it's worth checking directly: which specific AVSs is a given restaking pool or liquid restaking token actually securing, and what's each one's audit history and track record? What are the specific slashing conditions for each AVS, and are they clearly documented? Is the restaking protocol itself (EigenLayer or otherwise) audited and has it operated through real stress without incident? These questions matter more than headline reward rates, since the downside risk is what differentiates restaking from simple staking.

Bottom line

EigenLayer's restaking model lets Ethereum's existing staked capital extend economic security to new services, letting those services bootstrap trust faster than building an independent validator set from scratch — but it does this by adding new, AVS-specific slashing conditions on top of existing staking risk, not by making the underlying ETH safer. Understand exactly which AVSs any restaking position is exposed to before restaking, and treat the APY offered as compensation for real, specific additional risk rather than free extra yield.