Restaking takes ETH that is already staked and securing Ethereum’s base layer, and lets that same capital simultaneously secure additional services, without requiring a second, separate deposit. It is one of the more consequential ideas to come out of Ethereum’s ecosystem since the Merge, and it is worth understanding both what problem it solves and what new risk it introduces.
The problem restaking solves
Ethereum validators lock up 32 ETH to help secure the network and earn staking rewards in return. Plenty of other services, oracle networks, bridges, data availability layers, and various middleware, need their own economic security: a pool of capital that can be slashed (partially confiscated) if the service’s operators misbehave. Historically, each of these services had to bootstrap that security from scratch, convincing a new set of participants to lock up a new set of capital just for that one service. Restaking lets already-staked ETH opt in to additionally secure one or more of these services, extending Ethereum’s existing economic security outward instead of requiring every new service to build its own from zero.
How EigenLayer implements it
EigenLayer is the protocol that popularized this model. Validators (or holders of liquid staking tokens) opt in by depositing into EigenLayer’s smart contracts, which lets them additionally back what EigenLayer calls Actively Validated Services. Each AVS defines its own rules for what counts as misbehavior and what penalty applies, and restakers choose which AVSs to support, earning additional rewards from each one on top of their base ETH staking yield. The core trade is straightforward: more potential yield, in exchange for more potential slashing surface, since a mistake or exploit in any AVS a validator has opted into can now put a portion of their restaked ETH at risk, not just their base validator stake.
Liquid restaking tokens
Liquid restaking tokens extend the liquid staking model, where a token like a liquid staking receipt represents staked ETH and can be traded or used elsewhere in DeFi, to restaked positions specifically. A holder deposits ETH or an existing liquid staking token into a liquid restaking protocol, receives a liquid restaking token in return, and that token can then be used as collateral, traded, or deployed into other DeFi strategies, all while the underlying capital keeps earning both staking and restaking rewards. This makes restaked capital far more flexible, but it also stacks a third layer of smart contract risk, the restaking protocol itself, on top of the base staking and AVS risk already present.
The risk that matters most
How to size the risk honestly
The pitch for restaking is extra yield on capital that is already committed. The cost is that the same capital now answers to more than one set of rules. If you stake ether, you face one slashing condition. If that stake also secures three additional services, you face theirs too, and those conditions were written by different teams at different times with different amounts of scrutiny.
Three questions cut through most of the marketing. What exactly are you securing, and who wrote the slashing conditions for it. What is the actual yield after fees, and how much of it is paid in the protocol’s own token rather than in ether. And how would you exit if the position went wrong, given queue times, liquidity conditions for any receipt token you hold, and the possibility that everyone else is trying to exit at the same moment. If the yield is small and any of those answers are unclear, the trade is not being paid for the risk it carries.
Why correlation is the real danger
Individual slashing events are survivable. The scenario worth thinking about is correlated failure, where one bug or one misconfigured service triggers penalties across a large share of restaked capital simultaneously. That is a systemic risk rather than a personal one, and it is the reason this design attracts genuine criticism from people who are otherwise enthusiastic about the underlying idea. Diversification across operators helps. It does not remove the shared exposure at the base of the stack.
The core risk with restaking is correlation. A single pool of capital now backs multiple services simultaneously, which means a severe enough failure or exploit in one AVS could, in a worst case, cascade into losses that affect Ethereum’s base-layer staking security too, something that was never a risk when staked ETH only did one job. This is a genuinely new category of systemic risk in the Ethereum ecosystem, distinct from the transaction-level activity tracked in ETH Staking Flows and Validator Activity Explained, and it is the main reason restaking, despite its popularity, is still treated cautiously by more conservative validators and institutions.
Common questions
Is restaking the same as staking? No. Staking secures one network under one set of rules. Restaking commits the same capital to additional systems, each with its own conditions for losing it.
What is a liquid restaking token? A receipt token representing a restaked position that can be traded or used elsewhere while the underlying stake stays committed. It adds convenience and another layer of smart contract and liquidity risk.
Does restaking affect Ethereum’s security? Indirectly. Concentrating restaked capital in a small number of operators or services is the concern most often raised, rather than the mechanism itself.
Leave a Reply