Restaking

Restaking reuses already-staked assets to secure additional protocols: your staked ETH simultaneously backs Ethereum and extra services like oracles, bridges, rollups, and data layers, earning stacked rewards for stacked duties. EigenLayer pioneered the marketplace that makes this possible, turning idle staked capital into income-generating security for the rest of the ecosystem. How it works The mechanism is a contractual re-delegation of the same stake: Principal positions: you hold staked ETH (e.g., via liquid staking with Lido or a validator you run) and choose to apply it to EigenLayer "operators". AVSs (actively validated services): independent protocols — oracles, bridges, sequencers, fast-finality layers — lease the restaked security; in exchange they run their own slashing rules enforced on the Ethereum layer. Operator delegation: you pick an operator who runs the AVS software on your behalf; the operator's key handling is where your restaked capital lives and where slashing risk actually bites. Rewards & penalties: you earn base staking yield plus the AVS rewards the services pay for your security; if the service misbehaves (or your operator runs the software wrongly), the stake is slashed per the AVS's rules. EigenLayer's key design choice is that slashing is verifiable on Ethereum — the AVS doesn't get unilateral control of your capital; it must prove misbehaviour to slash, which is what makes the restaking market auditable at all. Why it matters for decentralization Restaking addresses a genuine bootstrap problem: new protocols asking for their own staked security force actors to choose between Ethereum security and new-service security. Restaking lets one capitalized stake secure both, which dramatically lowers the capital cost of new decentralized services — more services can afford to be decentralized rather than running trusted committees. The flip side is system-level: restaking compounds both yield and systemic risk. More rewards, but slashing in any one service can cascade into others that share the same stake, and a few giant restaking pools become single points of correlated failure. This is leverage on trust itself — powerful in calm markets, precisely the wiring that transmits the next crisis everywhere at once. The capital pillar of the W3D model scores this: who actually holds the concentrated stake determines whether "more security" means "more safety" or "more blast radius." Example: what an EigenLayer AVS restake looks like Classic use cases show the breadth: an oracle network needs economic guarantees that it reports honest prices, so it registers as an AVS and asks operators to pledge restaked ETH; a cross-chain bridge needs slashing-backed honesty for its watchers; a fast-finality layer promises sub-second confirmation with restaked ETH as the backstop. The operator that serves them runs all their software and can be slashed by any of them. Operators therefore stress diversification and professional infra — and the AVS/operator selection is exactly the concentration risk you should read before depositing. Well-known AVS families include oracle-adjacent, data-availability, sequencing, and cross-chain-messaging services registered on EigenLayer's mainnet. Restaking risks, itemized Correlated slashing: one shared stake backs many services; a single software bug or malicious AVS can slash all of them at once — diversification helps, but tail risks compound. Operator concentration: delegation flows to the largest, most professional operators, recreating the pool-centralization problem one layer up (LRT issuers included). Yield reflexivity: high AVS rewards attract stake, diluting returns while risk stays; late depositors often buy the risk without the early yield. Withdrawal gating: exits queue during stress and LRT prices gap below backing exactly when liquidity matters most. Governance capture: whoever controls the biggest restaked pools steers both Ethereum-adjacent votes and AVS rulebooks — a governance concentration that stakes as money cannot alone fix. What restaking is not Three confusions surface constantly in audits, and clearing them matters for honest risk reading: Not double staking your ETH: you are not deploying new capital into two networks. The same underlying stake backs Ethereum consensus and AVS duties; restaking multiplies attached commitments and slashing, not units of ETH. Not an EigenLayer-only feature: other designs (Jito Restaking, Symbiotic, Karak, and several L1-native mechanisms) pursue the same "shared security" market with different incentive and slashing arrangements. The audit question — operator set, AVS terms, exit mechanics — is identical wherever you land. Not free yield: AVS rewards are the price the service pays to borrow your economic security. If the reward exceeds the honest cost of that security, the AVS is either buying cheap insurance or the market is mispricing the risk you are now carrying. How to start restaking responsibly Map your exposure: list the AVSs an operator or pool serves; each adds an independent slashing surface to your one stake. Check operator diversification: prefer operators running distinct software and identity from every other operator you use — correlation across operators is what turns single-slashing into cascade events. Size the exit: understand withdrawal queues and cooling periods before committing; demand "how long does my capital stay locked under stress?" as a first-class question. Model the tail: stress-test a 5–25% slash against your portfolio, not just the APY. If the math fails, the yield was always the bait. Track one number: the W3D Ethereum and Solana audits expose the largest operators by restaked share; monitor concentration the same way you monitor any systemic metric. Dot these five dots and restaking becomes a legible risk instrument rather than a yield sticker — which is exactly how it should be read. Frequently asked questions Is restaking the same as staking ETH twice? Not in the double-spend sense: the same underlying stake backs Ethereum's consensus and AVS duties contractually, not twice-applied Nakamoto weights. Restaking multiplies attached responsibilities (and slashing), not the ETH itself. Can I lose my restaked ETH? Yes — that is the point of slashing. Misbehaviour by your operator or an AVS you are exposed to can cut the stake. Rates and triggers are AVS-specific; read each service's slashing contract before committing. Who actually runs the restaking services? Operators you delegate to, often large professional staking providers. Operator-set concentration is the single most important decentralization metric for restaked capital. Sources & methodology EigenLayer documentation — AVS framework and slashing design. L2Beat — risk profiles that include restaked-security exposure. W3D methodology + academy dataset. Related terms LRT token · Liquid staking · Staking · Validator · EigenLayer Chain audits: Ethereum · Solana · tool: Validator profit calculator