Restaking is one of those ideas that sounds conservative on the surface - you’re reusing existing stake, not creating new exposure - but the more closely you examine the mechanics, the less tidy it gets.
The core premise of EigenLayer, which pioneered the model on Ethereum, is straightforward: validators who have already staked ETH to secure Ethereum’s consensus layer can opt in to also secure additional protocols, called Actively Validated Services (AVSs). In exchange, they earn extra yield. The same ETH doing double (or triple) duty.
This is not hypothetical. EigenLayer went live on mainnet in 2023 and has attracted billions in restaked ETH since, with AVSs ranging from data availability layers to oracle networks and cross-chain bridges.
Where the Risk Actually Lives
The problem isn’t that restaking is fraudulent - it’s that the slashing conditions stack in ways that aren’t always legible to the validators taking on the exposure.
Slashing in Ethereum’s base layer is already somewhat rare and tightly scoped: double-signing, equivocation, specific provable misbehaviors. AVS slashing conditions are written by each AVS team independently. A validator opting into five AVSs has agreed to five different slashing regimes, some of which may be poorly specified, exploit-prone, or triggered by conditions entirely outside the validator’s control.
The stake being reused for each AVS isn’t partitioned. If a validator gets slashed by one AVS, that loss comes out of the same ETH securing Ethereum. This means an exploit or misconfiguration in a relatively obscure AVS could propagate damage back to Ethereum’s validator set - not at the protocol level, but at the economic level.
Pooled Restaking Makes This Murkier
Most retail participants don’t restake directly. They route through liquid restaking tokens (LRTs) - protocols like Renzo or Kelp that pool validator capacity and distribute it across AVSs. That pooling is efficient, but it also means individual depositors have limited visibility into which AVSs their stake is actually securing or what those AVSs’ slashing conditions look like.
LRTs have added another layer: their tokens are themselves being used as collateral in DeFi lending markets. So a slashing event doesn’t just affect the original depositor - it ripples through any protocol that accepted the LRT as collateral.
No One Has a Clean Answer Yet
The Ethereum research community has written seriously about correlated slashing risk under restaking, but the honest position is that the system hasn’t been stress-tested by a major slash event. The incentive structures make sense in calm conditions. What happens under adversarial conditions, or when an AVS is exploited and its slashing logic fires incorrectly, remains an open empirical question - not a solved one.