Restaking Risks: EigenLayer, Symbiotic and LRTs Explained

By Owen Thurm Published November 6, 2026 5 min read

Quick answer. Restaking stacks risks: the staking token's own, slashing by every service your operator secures, the restaking and LRT contracts, slow exits and bridges. Slashing is live on EigenLayer and set vault by vault on Symbiotic.

Watch: Restaking Risks: EigenLayer, Symbiotic and LRTs Explained 1:41

Video transcript

Restaking stacks risks. Each layer can add yield, and each one adds a new way to lose it.

Read a position from the bottom up: staking token, restaking protocol, services, LRT, bridge and lending market.

Slashing is live on EigenLayer mainnet, limited to each service's Unique Stake. On Symbiotic, it is set vault by vault. Queued EigenLayer withdrawals stay slashable for about fourteen days.

Redistribution raises the stakes. EigenLayer warns that a compromised service key can lead to theft of user funds.

LRT contracts add their own risk. In a 2024 Guardian review, a vault's restETH price fell whenever a withdrawal was queued. Rest resolved it.

In April 2026, a forged LayerZero message released 116,500 rsETH from Kelp DAO's adapter. LayerZero and Kelp differ on how the route came to rely on one verifier.

LRTs often back leverage loops: deposit, borrow ETH, restake, repeat. The rsETH loss moved into Aave, where LlamaRisk first modeled up to about 230 million dollars of bad debt.

So monitor every layer. Map the stack, read the slashing terms and track price against redemption rate. Check every bridge route, read the keys, and size to the weakest route.

Guardian's risk ratings score a position's code, control and dependencies from zero to one hundred. Read the full article, or talk to Guardian at guardian.security.

Restaking reuses staked ETH to secure other services. Each layer can add yield, and each adds a way to lose it.

A liquid restaking token (LRT) can fail at its own contracts, at the operators below it, or at a bridge far from Ethereum.

April 2026 showed the last one. A forged bridge message released 116,500 rsETH, and the loss reached Aave.

How Restaking Stacks Risk

Read a restaking position from the bottom up:

Layer	What can fail
Liquid staking token	Validator slashing, depeg, withdrawal queue
Restaking protocol	Core contract bugs, upgrades, pauses
AVS or network	Slashing logic, keys, governance
LRT	Accounting, oracles, admin keys, withdrawals
Bridge	Forged messages, single-verifier routes
Lending market	Liquidation cascades, bad debt

The bottom layer is in our guide to liquid staking risks, and validator penalties in Ethereum slashing risk. This post covers the layers above.

Slashing and AVS Risk

Restaking's new risk is slashing by services other than Ethereum. EigenLayer calls them AVSs; Symbiotic calls them networks.

EigenLayer

Slashing is live on EigenLayer mainnet under ELIP-002. Operators allocate a slice of delegated stake, called Unique Stake, to each AVS operator set.

Only that slice is slashable by that AVS. Within it, ELIP-002 says an AVS "may slash any Operator within any of their Operator Sets for any reason."

Slashing "does not have to be objectively attributable," and "no vetoes are provided by the EigenLayer protocol." ELIP-002 also warns that buggy slashing logic "may be deployed by AVSs."

Redistribution raises the stakes. Under ELIP-006, an AVS can send slashed funds to a recipient it names instead of burning them.

ELIP-006 warns that "a compromised AVS key can lead to theft of user funds when redistributable slashing is in use."

Two timers matter:

Withdrawals: queued withdrawals stay slashable for about 14 days.
Slashed funds: since release v1.13, now on mainnet, they wait about 7 days before they can be burned or redistributed.

Symbiotic

Symbiotic fixes each vault's slashing model at deployment: no slasher, an instant slasher, or a veto slasher whose resolvers can block a request.

So whether slashing is live has a per-vault answer. Read the slasher, veto window and resolvers before you deposit.

Symbiotic's docs warn that in restaking setups, "guarantees can be affected by slashing that happened on other networks."

Withdrawals stay slashable until the end of the next vault epoch. A vault's burner decides where slashed funds go: burned, redistributed or sent elsewhere.

LRT Contract and Withdrawal Risk

An LRT pools deposits, restakes them through operators and issues a token. Its contracts price that token and process exits.

Accounting is a common failure. In Guardian's 2024 review of Rest Finance's EigenLayer LST vault, the restETH price fell whenever a withdrawal was queued (High, VLT-1).

EigenLayer reduced the vault's shares at queueing, while restETH was burned only at completion. Rest resolved it.

The same review found withdrawals that would always revert against EigenLayer's then-live contracts (High, EWT-1). Building on a protocol that keeps upgrading is its own risk.

Exits are slow by design. An LRT's own queue sits on top of the restaking protocol's delay and Ethereum's exit queue.

Admin keys sit over all of it. Check who can upgrade the LRT, change its oracle, pause withdrawals or mint.

Bridge Risk: The rsETH Case

On April 18, 2026, a forged LayerZero message released 116,500 rsETH from Kelp DAO's adapter on Ethereum. LayerZero later valued it at about $292 million.

LlamaRisk reports the route was "configured as a 1-of-1 DVN" with no optional verifiers. LayerZero says attackers poisoned RPC nodes its verifier used, then forced failover with a DDoS.

The adapter backing rsETH on other chains fell from 116,723 rsETH to 223, against 152,577 rsETH of claims, per LlamaRisk.

The two sides differ on the setup:

LayerZero: it had advised Kelp to diversify verifiers, and the protocol "functioned exactly as intended."
Kelp: it told CoinDesk the setup "followed LayerZero's documented defaults," crypto.news reported.

Our full breakdown of the rsETH exploit covers the timeline and the fixes since.

Leverage Loops and Contagion

LRTs are popular collateral for loops: deposit the LRT, borrow ETH, restake, repeat. A small discount can liquidate the whole loop.

On April 24, 2024, Renzo's ezETH fell as low as $750 on Uniswap, CoinDesk reported.

Observers it quoted cited liquidations on Gearbox and Morpho, and said liquidated loopers deepened the slide.

In April 2026, the rsETH loss moved into lending. Attacker addresses supplied 89,567 rsETH on Aave and borrowed 82,650 WETH and 821 wstETH, per LlamaRisk.

LlamaRisk first modeled $123.7 million to $230.1 million of bad debt, depending on how the loss was shared. It said Aave's contracts "were not compromised."

By May 9, liquidations had recovered 106,993 rsETH. LlamaRisk said the DeFi United coalition's committed ETH would cover the rest.

For lenders, an LRT is only as safe as its weakest chain and route.

Monitoring Restaking Exposure

Map the stack. Each LRT's LSTs, operators, AVSs or networks, bridges and lending venues.
Read slashing terms. Unique Stake per AVS; slasher type, veto window and resolvers per vault.
Flag redistribution. Note redistributable operator sets and who controls the recipient.
Watch allocations. Alert on new AVS registrations, allocation changes and any slash.
Track the rate. Market price against redemption rate, and pool depth.
Know the exit. The LRT queue, the restaking delay, then Ethereum's exit queue.
Check every route. The verifier setup on each chain the LRT is bridged to.
Read the keys. Who can upgrade, pause, mint or change the oracle, and with what delay.
Size to the weakest route. Caps and LTVs should assume the worst chain fails.

How Guardian Helps

For allocators, Guardian's risk ratings underwrite a position's deployed code, control, dependencies and economic paths, and score it from 0 to 100.

Monitoring then flags upgrades, signer and role changes, and dependency drift such as "a bridge route added," the day they happen.

For issuers, Managed Security monitors contracts on every block and reviews every multisig transaction before it is signed.

Frequently Asked Questions

What are the main risks of restaking?

Slashing by AVSs or networks, bugs in restaking and LRT contracts, slow withdrawals, LRT discounts, admin keys and bridges. They sit on top of the liquid staking token's own risks.

Is slashing live on EigenLayer and Symbiotic?

On EigenLayer, yes: ELIP-002 slashing is live on mainnet, and only allocated Unique Stake is slashable. On Symbiotic it depends on the vault, which fixes its slasher at deployment; some vaults have none.

What happened to rsETH in April 2026?

A forged LayerZero message released 116,500 rsETH from Kelp DAO's Ethereum adapter, on a route with one verifier. LlamaRisk first modeled $123.7 million to $230.1 million of bad debt on Aave; liquidations later recovered 106,993 rsETH.

How long does it take to withdraw from EigenLayer?

EigenLayer's withdrawal delay is about 14 days (100,800 blocks), and funds stay slashable during it. An LRT's own queue and Ethereum's exit queue can add more.

Sources

Underwrite every layer of a restaking position

Guardian reviews the code, keys, operators and bridges behind an LRT, then flags the upgrades and route changes that move its risk.

Talk to Guardian