Restaking is a way to use assets already committed to Ethereum staking to help secure other services. EigenLayer is one protocol built around this idea: stakers can opt in, or delegate to operators who opt in, to help secure Actively Validated Services (AVSs). Some services may offer additional rewards, but restaking does not promise a fixed return or give an AVS all of Ethereum’s security guarantees.
How restaking works
With native restaking, an Ethereum validator connects its staked ETH to a restaking protocol. A person who stakes through a liquid staking provider may instead hold a liquid staking token (LST) and deposit that token into a supported restaking service. In either case, the underlying stake is being used under additional rules. It is no longer exposed only to Ethereum’s own validator duties.
EigenLayer calls the services being secured AVSs. They can include systems such as data availability services, oracles, bridges, or other infrastructure. Operators run the software an AVS requires. Stakers can operate services themselves or delegate their stake to an operator. The operator’s participation and any rewards depend on the service and its terms; depositing into EigenLayer alone does not mean every AVS is being secured.
The appeal for a new service is that it may draw on stake and operators already present in the ecosystem instead of building a new validator network from scratch. The limit is just as important: an AVS gets the economic guarantees created by the stake allocated to it and by its own rules. It does not automatically inherit Ethereum’s consensus, fault tolerance, or protection against every kind of attack. Ethereum.org’s guide to restaking distinguishes the AVSs that receive this additional security from Ethereum’s base-chain staking.
EigenLayer’s slashing model
EigenLayer’s slashing feature went live on mainnet in April 2025. Slashing is a penalty that can reduce or permanently lock stake when an operator breaks a service’s stated commitments. The feature is not an automatic penalty applied to every EigenLayer deposit: operators opt into slashable Operator Sets, and the service defines the conditions attached to its work. The EigenLayer launch announcement describes this opt-in model and the introduction of Operator Sets.
The protocol design also uses Unique Stake allocations. Under ELIP-002, an operator allocates portions of its delegated stake to particular Operator Sets, and each allocation is assigned to a set rather than being freely slashable by every AVS at once. This can limit direct overlap between slashing exposures. It does not remove the need to understand an AVS’s rules, the operator’s configuration, or the software that decides whether a commitment was met.
Where the extra risk comes from
Restaking adds obligations and possible failure points. Operators must run additional software and meet each service’s requirements. A service may define a slashable failure differently from Ethereum’s own consensus rules. A mistake in an operator’s setup, a bug in an AVS, or a disputed penalty can therefore matter to the people whose stake was allocated to that service. Operators and delegators also need to understand which services their chosen operator supports and which stake allocations are slashable.
Liquid restaking adds another layer. A liquid restaking token represents a position managed by its issuer; it may have separate smart-contract, liquidity, redemption, or pricing risks. The token’s market price is not a guarantee that it can be redeemed immediately at the value of the underlying assets. Restaked assets can also have withdrawal or unbonding delays. Ethereum.org’s current overview lists slashing, operator concentration, correlated exposure across services, and withdrawal waits among the risks users should consider.
Why the design is debated
Supporters see a possible way for new infrastructure to obtain economic backing without creating a separate token and validator set. Critics ask whether a growing set of services could make validators more dependent on a small group of operators, add software duties, or connect risks that users may not be able to evaluate. The answer depends on the specific AVS, its slashable stake, the operator set, and the service’s ability to enforce its rules; a headline yield or total-value figure cannot answer those questions on its own.
A separate question is whether a serious failure in an application built on shared stake could create pressure for Ethereum’s wider community to intervene. In “Don’t overload Ethereum’s consensus,” Vitalik Buterin argues that applications should not assume Ethereum’s social layer will reverse losses or settle their disputes. That is a warning about expectations and system boundaries, not a prediction that a particular AVS failure will cause a fork. EigenLayer’s opt-in participation and stake-allocation design aim to keep obligations explicit, but whether those boundaries remain effective as services grow is an ongoing design question.
What restaking does—and does not—provide
Restaking lets participants choose to use staked assets to support additional services, and it gives those services a way to make economic commitments to users. The extra use comes with extra rules, operator dependencies, and possible penalties. To understand a particular position, identify the AVS, the operator, the stake allocated to it, its slashable conditions, the reward terms, and the withdrawal path. The label “restaked” by itself does not tell you how secure a service is or what a user will recover after a failure.
Related Articles
- Is Ethereum Staking Making the Network More Centralized?
- Are Layer 2 Networks Actually Decentralized?
- Why Smart Contract Audits Fail: What Post-Mortems Reveal About the Limits of Security Reviews
Related Glossary Terms
See Also
Sources
- Ethereum.org, “What is restaking?” — participants, AVSs, native and liquid restaking, and current risk categories.
- EigenLayer, “Slashing Goes Live on Mainnet” — April 2025 activation, Operator Sets, and opt-in slashing.
- EigenLayer Improvement Proposal 002 — Unique Stake, Operator Sets, and the protocol’s slashing design.
- Vitalik Buterin, “Don’t overload Ethereum’s consensus” — an argument about application risks and the limits of Ethereum’s social layer.