Liquid Restaking Explained: Staking Your ETH Twice (Sort Of)

Staking ETH already felt like a full-time commitment: lock up your coins, run or delegate to a validator, and earn a modest yield for helping secure Ethereum. Then restaking showed up and asked a strange question — what if that same staked ETH could secure other networks at the same time, for extra rewards?

That's the pitch behind restaking, and it's become one of the fastest-growing corners of crypto infrastructure. Understanding it means understanding what validators are actually selling: not compute, not storage, but trust.

A validator's real product is "cryptoeconomic security" — a pile of staked capital that gets destroyed (slashed) if the validator misbehaves. Ethereum uses this to keep its own validators honest. Restaking protocols, pioneered by EigenLayer, realized that same staked capital could back other services too: oracles, bridges, data availability layers, and other young networks that need a trust guarantee but don't want to bootstrap their own validator set from scratch.

In practice, a staker opts in to extra slashing conditions tied to these additional services ("actively validated services," or AVSs) in exchange for extra yield on top of normal staking rewards. The same ETH is now backstopping multiple systems at once.

Restaking directly requires running validator infrastructure and manually opting into AVSs — not something most holders want to do themselves. Liquid restaking tokens (LRTs) abstract that away. Deposit ETH (or an existing liquid staking token like stETH) into a liquid restaking protocol, and you receive a tradable receipt token representing your restaked position. The protocol handles validator operations and AVS selection; you keep a token you can use elsewhere in DeFi — as collateral, in a liquidity pool, or simply held while it accrues yield.

This mirrors exactly what liquid staking tokens did for plain staking: turn an illiquid, locked position into a composable DeFi asset. LRTs just add a second layer of yield and a second layer of complexity on top.

Stacking yields means stacking risks, and restaking adds several that don't exist in plain staking:

• Slashing risk multiplies. Your ETH can now be penalized for misbehavior in the AVSs it secures, not just for Ethereum consensus faults. A bug in an unrelated AVS can cost you money.

• Smart contract risk compounds. You're now trusting the restaking protocol's contracts, the liquid token's contracts, and every AVS's contracts — each an independent point of failure.

• New AVSs are unproven. Many services seeking restaked security are early-stage and haven't been tested under adversarial conditions the way Ethereum consensus has over years of mainnet operation.

• Liquidity and peg risk. LRTs can trade below the value of the ETH backing them during stress, the same way liquid staking tokens occasionally depeg during volatility.

Restaking solves a real coordination problem: new networks that need security today would otherwise have to convince validators to bootstrap a brand-new token from zero, which is slow and capital-inefficient. Tapping into Ethereum's existing multi-billion-dollar validator set instead lets them launch faster and more securely. For stakers, it turns idle collateral into a second income stream without giving up their original staking position.

Restaking is a genuinely clever reuse of existing security — but "reuse" means the same capital is now on the hook for more failure modes, not fewer. Extra yield is compensation for extra risk, not a discount on it. Before restaking ETH or holding an LRT, know which AVSs your capital actually secures, what could get it slashed, and whether the yield on offer is worth stacking that much additional exposure on a single pile of collateral.