Restaking means reusing ETH that is already staked to secure Ethereum as collateral for other services too. EigenLayer is the protocol that popularized it: stakers opt in to extra rules, delegate their stake to operators who run software for those services, and earn extra rewards. The catch is extra slashing risk: break a service's rules and part of the same stake can be taken. It is a way to rent Ethereum's economic security, and it layers new risks on top of normal staking.
The problem restaking tries to solve
Many systems need their own security. Examples include oracles, bridges, data availability layers and networks that verify off-chain computation. Each one usually needs a set of operators who put up collateral that can be taken, or slashed, if they cheat.
Building that from scratch is hard. A new project typically launches its own token and asks people to stake it. That security is only as strong as the token's value, which is often small and volatile. The project also has to recruit and coordinate a fresh set of operators.
Ethereum, meanwhile, already has a very large pool of staked ETH. Restaking asks: what if that same stake could also back other services, if stakers choose to accept the extra rules?
Key terms
- Restaker. Someone who commits staked ETH, or tokens that represent it, to EigenLayer.
- Operator. An entity that runs the software for one or more services. Restakers delegate their stake to operators.
- AVS (Actively Validated Service). A service secured through EigenLayer, such as a data availability layer, an oracle network or a coprocessor. Each AVS defines its own tasks, rewards and slashing conditions.
- Slashing. Taking away part of a staker's collateral as punishment for provably breaking the rules.
How EigenLayer works
- A restaker deposits. There are two main routes, covered below: native restaking and restaking liquid staking tokens.
- The restaker delegates to an operator. The operator will do the actual work. Restakers choose operators based on reputation, fees and which services they support.
- The operator opts in to AVSs. Each AVS sets its own requirements. The operator runs that AVS's software, such as nodes that store data or sign off on results.
- The operator allocates stake. The operator commits part of its delegated stake to each AVS it serves. That stake becomes slashable under the AVS's rules.
- Rewards flow back. AVSs pay rewards, often in their own tokens, which are shared between operators and the restakers who delegated to them.
- Misbehavior is punished. If an operator breaks an AVS's rules, that AVS can slash the stake allocated to it. Restakers who delegated to that operator share the loss.
The core contracts live on Ethereum. The AVS work itself usually happens off-chain, with results or proofs reported back on-chain where needed.
Native restaking vs. liquid restaking
| Route | What you deposit | How it works | Trade-offs |
|---|---|---|---|
| Native restaking | Your own validator's stake | Point your validator's withdrawal credentials to an EigenPod contract | Needs 32 ETH and a validator; no extra token contract risk |
| LST restaking | Liquid staking tokens such as stETH or rETH | Deposit the tokens into EigenLayer strategy contracts | Easy to access; adds the LST's own risks |
| Liquid restaking tokens (LRTs) | ETH or LSTs deposited into a third-party protocol | The protocol restakes for you and gives you a tradable token | Most convenient; adds another protocol, its operator choices and its liquidity risk |
Withdrawal credentials are the Ethereum address a validator's stake returns to when it exits. Pointing them at an EigenPod, a contract controlled by EigenLayer on your behalf, means EigenLayer can enforce slashing before your ETH is released.
Liquid restaking tokens such as ether.fi's eETH or Renzo's ezETH work like liquid staking tokens, but one layer further out. They pool deposits, choose operators and AVSs, and hand users a token that can be used in DeFi.
What slashing looks like in practice
For a long time after launch, EigenLayer ran without slashing. Operators could opt in to services, but there was no penalty for misbehaving. Slashing was enabled on mainnet in 2025, along with operator sets, which let an AVS group operators and define how their stake can be slashed.
An important design choice is unique stake allocation. An operator allocates a specific portion of its stake to each AVS. That portion can only be slashed by that AVS. This limits contagion: a bug or unfair slash in one service should not wipe out stake allocated to another.
Withdrawals also come with a delay. When you leave EigenLayer, your stake remains slashable for a period before it is released. This stops operators from misbehaving and exiting before a penalty can be applied. Native restakers who fully exit also wait in Ethereum's own validator exit queue.
Examples of what AVSs do
- Data availability. EigenDA, built by Eigen Labs, stores data for rollups so that anyone can check it was published. Operators attest that they hold the data.
- Oracles and bridges. Networks that report prices or cross-chain messages can require operators to back their reports with slashable stake.
- Coprocessors and verification. Services that run heavy computation off-chain and have operators vouch for the result.
The common thread is that each service gains security backed by ETH instead of launching a fresh stake from zero.
The risks
Stacked slashing risk
Restaked ETH faces Ethereum's slashing rules plus the rules of every AVS it is allocated to. Each AVS's slashing logic is new code, written by a different team. A bug in that logic could slash honest operators. Unique stake allocation limits how far one bad slash spreads, but restakers still carry the risk for every service their operator joins.
Operator risk
Restakers usually do not run the AVS software themselves. They trust operators to run it correctly and to choose sensible services. An operator that joins many risky AVSs for extra rewards exposes all of its delegators.
Smart contract risk in layers
A typical LRT position depends on several sets of contracts: the liquid staking protocol, EigenLayer, the LRT protocol, and often a DeFi protocol where the LRT is used. A failure in any layer can cause losses.
Liquidity and depeg risk
LRTs can trade below the value of their underlying assets, especially when withdrawals involve long delays. In April 2024, Renzo's ezETH briefly fell sharply below its backing on decentralized exchanges during a rush to exit, which triggered liquidations for users with leveraged positions.
Yield that may not last
Early restaking demand was driven heavily by points programs, off-chain scores that users hoped would turn into token airdrops. Rewards from AVSs depend on those services generating real revenue. Headline yields should be treated with care.
Risk to Ethereum itself
Some Ethereum researchers, including Vitalik Buterin in a 2023 post, have warned against using restaking in ways that expect Ethereum's own consensus to step in if a service fails. If a large share of staked ETH were exposed to the same failing service, the fallout could create pressure on Ethereum's social layer. EigenLayer's design aims to keep AVS failures contained to the stake that opted in.
EigenLayer and its alternatives
EigenLayer is the largest restaking protocol on Ethereum, but it is not the only one. Protocols such as Symbiotic and Karak offer similar shared security with different designs, such as accepting a wider range of collateral types. The core idea, one stake backing many services, is the same.
Key takeaways
- Restaking reuses staked ETH to secure additional services in exchange for extra rewards.
- In EigenLayer, restakers delegate to operators, who run software for Actively Validated Services (AVSs).
- You can restake natively through an EigenPod, deposit liquid staking tokens, or hold a liquid restaking token.
- Each AVS can slash the stake allocated to it, so risk stacks on top of normal staking.
- Unique stake allocation and withdrawal delays are designed to limit contagion and prevent quick exits.
- Layered contracts, operator choices and LRT liquidity are the main risks to check before restaking.
Get the weekly commit
New blockchain deep dives every week.
