Restaking Explained — How EigenLayer, Lido, and Kelp Let You Double-Dip Your Staked ETH (And the Risks Most Guides Ignore)
Published on 2026-06-13
Your Staked ETH Is Leaving Money on the Table — Or Is It?
If you're staking ETH and only earning staking rewards, you're leaving yield on the table. That's the pitch behind restaking — the fastest-growing primitive in DeFi, with over $25 billion in total value locked across restaking protocols as of mid-2026.
The concept is elegant: your staked ETH already secures the Ethereum blockchain. Restaking lets you use that same staked ETH to simultaneously secure additional services — oracles, data availability layers, cross-chain bridges, AI inference networks, and more. You earn staking yield plus restaking rewards. Double-dip, no extra capital required.
But here's what the hype threads don't tell you: restaking doesn't just add yield — it stacks risk. Every additional protocol you secure with your staked ETH is another smart contract that can be exploited, another slashing condition that can trigger, another point of failure between you and your principal.
The Anti-Loss Protocol for restaking is about understanding those stacked risks before you opt in. Because once your restaked position is slashed on a secondary protocol, there's no appeal process — your staked ETH is gone, and your primary Ethereum stake may be affected too.
How Restaking Actually Works
To understand restaking, you need to understand what your staked ETH is doing. When you stake ETH (either solo or via Lido/Rocket Pool), your tokens secure Ethereum's consensus layer. Validators propose blocks, attest to transactions, and earn rewards for honest behavior. If they misbehave, they get slashed — losing a portion of their stake.
Restaking takes this one step further. Instead of your staked ETH only securing Ethereum, it also secures additional protocols called Actively Validated Services (AVSs). These are external systems that need cryptoeconomic security — economic guarantees that validators will behave honestly because they have something to lose.
The flow works like this:
- You hold staked ETH (or a liquid staking token like stETH, rETH, or cbETH).
- You restake those tokens by depositing them into a restaking protocol (EigenLayer, Kelp, Symbiotic, etc.).
- The restaking protocol assigns your restaked tokens to one or more AVSs — external protocols that need security.
- You earn Ethereum staking yield (from your original stake) + restaking rewards (from the AVSs).
- If the AVS detects misbehavior, it can trigger slashing — destroying a portion of your restaked ETH.
The key insight: your ETH is now securing multiple systems simultaneously. A single validator key can be slashed on Ethereum (for consensus violations) and on one or more AVSs (for service-specific violations). These are independent slashing conditions — and they can trigger simultaneously.
The Major Restaking Protocols
EigenLayer (The Market Leader)
EigenLayer is the original restaking protocol and still the dominant player, with over $18 billion in TVL. Built on Ethereum, EigenLayer lets ETH stakers and LST holders restake their assets to secure AVSs. Key features:
- Accepts: Native staked ETH (via beacon chain withdrawal credentials), stETH (Lido), rETH (Rocket Pool), cbETH (Coinbase), and 10+ other LSTs.
- AVS ecosystem: 50+ active AVSs including EigenDA (data availability), AltLayer (rollup automation), Oracle Networks, and cross-chain messaging protocols.
- Slashing model: Each AVS defines its own slashing conditions. Slashing is enforced by the EigenLayer smart contracts on Ethereum — it's trustless and on-chain.
- Operator delegation: You can delegate to a Node Operator who chooses which AVSs to run, or you can self-operator if you run validator infrastructure.
- Rewards: Variable by AVS. Typical restaking APY ranges from 2–8% on top of base staking yield (3.5–4.5%).
Kelp (Multi-Chain Restaking)
Kelp (formerly Kelp DAO) offers restaking across multiple chains — not just Ethereum. It supports rsETH (restaked ETH) and agETH (restaked via EigenLayer + additional strategies). Key differentiator: Kelp aggregates restaking opportunities across chains and auto-compounds rewards.
- Multi-chain: Ethereum, Arbitrum, Base, Linea, and expanding.
- rsETH token: Liquid restaking token that accrues both staking and restaking yield. Tradeable and usable in DeFi.
- Risk layering: Kelp adds its own "risk curator" layer that evaluates AVSs before allowing them into the pool. This adds a (imperfect) filter against the riskiest AVSs.
Symbiotic (Permissionless Restaking)
Symbiotic takes a different approach: it's a permissionless restaking protocol where any network can request security from any vault of assets. Unlike EigenLayer (which is ETH-centric), Symmatic supports restaking of any ERC-20 token — not just ETH and LSTs.
- Asset support: ETH, LSTs, stablecoins (USDC, USDT), LP tokens, and any whitelisted ERC-20.
- Vault-based: Users deposit into vaults managed by operators. Each vault has its own slashing conditions and AVS set.
- TVL: $4B+ and growing rapidly, particularly among users who want to restake non-ETH assets.
Lido + EigenLayer (Staked ETH Restaking)
Lido — the largest liquid staking protocol — has integrated with EigenLayer to let stETH holders restake directly through the Lido interface. This is the most user-friendly path: if you already hold stETH, you can restake it in two clicks without moving assets.
- Process: Deposit stETH into EigenLayer via Lido's interface → receive eETH (EigenLayer-restaked ETH).
- Yield: Base staking yield (~3.5%) + EigenLayer restaking rewards (2–6% depending on AVS selection).
- Liquidity: eETH is tradeable, so you maintain liquidity while earning restaking yield.
Restaking Yield Comparison
| Strategy | Base Yield | Restaking Bonus | Total APY (Est.) | Risk Level |
|---|---|---|---|---|
| Ethereum solo staking | 3.5–4.5% | None | 3.5–4.5% | Low |
| Lido stETH (no restaking) | 3.2–4.0% | None | 3.2–4.0% | Low |
| EigenLayer (1–2 conservative AVSs) | 3.5–4.5% | 1.5–3.0% | 5.0–7.5% | Low-Medium |
| EigenLayer (3–5 AVSs) | 3.5–4.5% | 3.0–6.0% | 6.5–10.5% | Medium |
| Kelp rsETH (diversified) | 3.2–4.0% | 2.0–4.0% | 5.2–8.0% | Low-Medium |
| Symmatic (ETH vault) | 3.5–4.5% | 2.0–5.0% | 5.5–9.5% | Medium |
| Symmatic (stablecoin vault) | None (no staking) | 3.0–7.0% | 3.0–7.0% | Medium-High |
| Lido + EigenLayer (eETH) | 3.2–4.0% | 2.0–4.0% | 5.2–8.0% | Low-Medium |
The 6 Major Restaking Risks
Risk 1: Cascading Slashing
This is the big one. When you restake, your ETH is subject to multiple independent slashing conditions. If you're securing three AVSs and one of them detects a violation (real or erroneous), it can slash your stake. Worse, slashing on one AVS can trigger a cascade: if your validator's balance drops below the threshold for one service, it may be forcibly exited from others, creating a domino effect.
In Q1 2026, a bug in an oracle AVS caused 47 validators to be simultaneously slashed for a condition that was later determined to be a false positive. The slashing was valid and irreversible. Affected restakers lost 0.5–2.0% of their staked ETH — on top of any market losses during the incident.
Risk 2: Smart Contract Risk (Compounded)
Restaking adds layers of smart contracts between you and your ETH. You're trusting the restaking protocol's contracts (EigenLayer, Kelp, Symbiotic), the AVS contracts, and the operator's infrastructure. A bug in any of these layers can result in loss of funds.
EigenLayer has been extensively audited (Trail of Bits, OpenZeppelin, Spearbit), but the AVSs it secures vary wildly in audit quality. Some AVSs are battle-tested; others are experimental protocols with a single audit from an unknown firm. When you restake into multiple AVSs, you're taking on the risk of the weakest contract in the set.
Risk 3: Liquidity Risk
Restaked positions may have lock-up periods or withdrawal queues. EigenLayer's withdrawal process requires an unbonding period (typically 7–21 days depending on the AVS) plus potential additional queue time during high-demand periods. If the market crashes and you need to exit, your restaked ETH is locked.
Liquid restaking tokens (eETH, rsETH) mitigate this by being tradeable, but they can depeg — just like stETH can depeg from ETH. During the March 2026 correction, rsETH briefly traded at a 3.8% discount to ETH on major DEXs.
Risk 4: Operator Risk
If you delegate to a Node Operator (rather than running your own infrastructure), you're trusting that operator to run AVS software correctly. An operator who misconfigures an AVS client, runs outdated software, or experiences extended downtime can trigger slashing that affects all their delegators.
In 2025, a mid-tier operator running 12 AVSs experienced a configuration error that caused simultaneous downtime across 8 services. Delegators were slashed on 5 of those 8 AVSs, losing an average of 1.2% of their restaked ETH.
Risk 5: AVS Failure Risk
The AVSs you're securing may fail as businesses. If an AVS shuts down, loses funding, or is exploited, the slashing conditions may trigger in ways that weren't anticipated. Some AVSs have "liveness" slashing — if the AVS itself goes offline, validators can be penalized for not serving a service that no longer exists.
Risk 6: Regulatory Uncertainty
Restaking is new enough that regulators haven't fully addressed it. The SEC has signaled that certain staking derivatives may be securities; restaking derivatives (eETH, rsETH) are even further removed from the underlying asset. If regulations change, restaking protocols could face enforcement actions that affect users' ability to withdraw or trade their positions.
Restaking Risk Comparison by Protocol
| Protocol | Slashing Risk | Smart Contract Risk | Liquidity Risk | Operator Risk | Best For |
|---|---|---|---|---|---|
| EigenLayer (self-operator) | Medium (you control AVS selection) | Low (extensively audited) | Medium (7–21 day unbonding) | None (you run the infra) | Experienced validators |
| EigenLayer (delegated) | Medium-High (operator chooses AVSs) | Low | Medium | Medium-High (depends on operator) | LST holders who want passive yield |
| Kelp rsETH | Low-Medium (risk curator filter) | Medium (additional contract layer) | Low (tradeable rsETH) | Low-Medium (diversified operators) | Users wanting liquid restaking |
| Symbiotic (ETH vault) | Medium (vault-dependent) | Medium (newer protocol) | Medium | Medium (vault operator) | Users wanting permissionless options |
| Symmatic (stablecoin vault) | Medium-High (no staking base) | Medium | Low (tradeable) | Medium | Stablecoin holders seeking yield |
| Lido + EigenLayer (eETH) | Low-Medium (conservative AVS set) | Low (Lido + EigenLayer) | Low (tradeable eETH) | Low (Lido's operator set) | Existing stETH holders |
The Anti-Loss Protocol: 8 Rules for Safe Restaking
Rule 1: Start with Conservative AVSs Only
Not all AVSs are created equal. When choosing which AVSs to secure (or which operator to delegate to), prioritize:
- Battle-tested AVSs: EigenDA, established oracle networks, and protocols that have operated for 6+ months without incidents.
- Simple slashing conditions: Prefer AVSs with clear, objective slashing rules (e.g., "sign conflicting attestations") over subjective ones (e.g., "provide inaccurate data" — who decides what's inaccurate?).
- Low slashing penalties: AVSs that slash 0.1% for a first offense are less risky than those that slash 10%.
Rule 2: Limit Your AVS Exposure
Don't restake into every available AVS. Each additional AVS adds another slashing condition, another smart contract dependency, and another potential point of failure. For most users, 1–3 conservative AVSs is the sweet spot between yield optimization and risk management.
Rule 3: Choose Operators Carefully
If you're delegating (not self-operating), vet your operator:
- Track record: How long have they been operating? Have they ever been slashed?
- AVS selection: Do they run a conservative or aggressive AVS portfolio? Check their EigenLayer dashboard.
- Infrastructure: Do they run redundant nodes? What's their historical uptime?
- Transparency: Do they publish performance reports? Are they responsive in their community channels?
Rule 4: Monitor Your Restaked Positions
Restaking is not "set and forget." Set up monitoring for:
- Operator health: Is your operator online and performing well across all AVSs?
- Slashing events: Monitor EigenLayer's slashing dashboard and your operator's status.
- LST depeg: If you hold eETH or rsETH, monitor the price relative to ETH. A depeg above 2% signals market stress.
- AVS status: Is the AVS you're securing still operational? Has it been deprecated or exploited?
Rule 5: Keep a Liquid Reserve Outside Restaking
Never restake 100% of your staked ETH. Keep a liquid reserve — either unstaked ETH, stablecoins, or non-restaked LSTs — so you can cover emergencies without waiting for the unbonding period. A good rule: restake no more than 50% of your staked position.
Rule 6: Understand the Withdrawal Process Before You Enter
Before restaking, know exactly how to exit:
- What is the unbonding period? (EigenLayer: 7–21 days depending on AVS)
- Is there a withdrawal queue beyond the unbonding period?
- Can you sell the liquid restaking token instead of unbonding?
- What are the gas fees for withdrawal?
Rule 7: Prefer Liquid Restaking Tokens for Flexibility
If you're not running your own validator, liquid restaking tokens (eETH, rsETH) offer a meaningful advantage: you can exit by selling the token on a DEX rather than waiting for the unbonding period. Yes, you take on depeg risk — but in a crisis, liquidity is worth more than a small discount.
Rule 8: Don't Chase the Highest APY
The highest restaking yields come from the newest, most experimental AVSs — the ones with the least battle-tested code and the most aggressive slashing conditions. A strategy earning 12% APY with 5 experimental AVSs is not better than one earning 6% APY with 2 conservative AVSs. The expected value accounts for the probability of slashing — and that probability is higher than most users estimate.
Restaking Safety Scorecard
| Safety Factor | Best Practice | Risk If Ignored |
|---|---|---|
| AVS diversification | 1–3 conservative AVSs maximum | Each additional AVS adds independent slashing risk |
| Operator vetting | Check track record, uptime, AVS selection | Operator misconfiguration = your slashing loss |
| Liquid reserve | Keep 50% of staked ETH outside restaking | Locked funds during market crash = forced losses |
| Withdrawal awareness | Know unbonding period + queue before entering | Can't exit during crisis = maximum drawdown |
| Depeg monitoring | Alert if LST depeg exceeds 1.5% | Selling during depeg locks in additional loss |
| Smart contract awareness | Only restake via audited protocols (EigenLayer, Lido) | Unaudited contract = potential total loss |
| Yield realism | Prefer 5–7% APY over 12%+ APY | High APY = high slashing probability |
| Regulatory awareness | Monitor SEC/CFTC guidance on restaking derivatives | Regulatory action = forced unwind at bad prices |
Who Should (and Shouldn't) Restake
Restaking is right for you if:
- You already hold staked ETH or LSTs and want additional yield.
- You understand smart contract risk and accept it consciously.
- You have a liquid reserve outside your restaked position.
- You're comfortable with 7–21 day withdrawal timelines.
- You actively monitor your positions (or use a trusted operator with transparent reporting).
Restaking is NOT right for you if:
- Your staked ETH represents your entire crypto portfolio (concentration risk).
- You need liquidity within 7 days (unbonding period is too long).
- You don't understand how slashing works on the AVSs you're securing.
- You're chasing the highest APY without evaluating the underlying risk.
- You can't afford to lose 1–5% of your staked ETH to a slashing event.
Bottom Line
Restaking is a genuine innovation — it lets ETH stakers earn additional yield by providing security to protocols that need it. The infrastructure (EigenLayer, Kelp, Symbiotic) is maturing rapidly, and the AVS ecosystem is expanding into real use cases: data availability, oracle networks, AI inference, and cross-chain messaging.
But restaking is not free money. It stacks risk on top of risk: multiple slashing conditions, additional smart contract dependencies, operator risk, liquidity constraints, and regulatory uncertainty. The extra 2–5% APY is compensation for taking on these risks — and for many users, it's adequate compensation if managed carefully.
The Anti-Loss Protocol for restaking is straightforward: start with conservative AVSs, limit your exposure, choose operators carefully, keep a liquid reserve, monitor actively, and never chase the highest yield at the expense of safety. Your staked ETH is your crypto foundation — restaking should enhance your returns, not jeopardize your principal.
Before restaking, compare network fees, unbonding periods, and AVS options at Crypto Network Guide — because the best restaking strategy starts with choosing the right network and the right protocol for your risk tolerance.