Liquid Restaking Tokens Compared: EtherFi vs Renzo vs Kelp

Choosing a liquid restaking token in 2026 is not the same decision it was in 2024. Back then, the question was which protocol would capture the most EigenLayer airdrop points. Now the question is which protocol you can trust with your ETH after a $292 million bridge exploit hit one of the three market leaders. EtherFi, Renzo, and Kelp DAO all let you stake ETH, restake it through EigenLayer, and hold a liquid token that keeps earning while you use it elsewhere in DeFi. But they differ sharply on security architecture, token design, fee structure, and what happens when something breaks. This comparison looks at what actually separates them so you can decide which one, if any, deserves your ETH right now.

Panaprium ist unabhängig und wird vom Leser unterstützt. Wenn Sie über unseren Link etwas kaufen, erhalten wir möglicherweise eine Provision. Wenn Sie können, unterstützen Sie uns bitte monatlich. Die Einrichtung dauert weniger als eine Minute und Sie werden jeden Monat einen großen Beitrag leisten. Danke schön!

What Liquid Restaking Actually Does

Liquid restaking takes ETH you have already staked and routes it through EigenLayer to secure additional services, called Actively Validated Services (AVSs). In return, you get a liquid token like weETH, ezETH, or rsETH that represents your restaked position plus accumulated rewards. You can trade it, use it as collateral, or drop it into a liquidity pool while your underlying ETH keeps earning both staking yield and AVS rewards. For a deeper technical breakdown of how EigenLayer restaking works and why it exists, see Liquid Restaking Explained: EigenLayer and Beyond.

The tradeoff is layered risk. You are exposed to smart contract risk in the restaking protocol, slashing risk from the AVS, oracle risk if the token price feed breaks, and often bridge risk if the token moves across chains. That last risk turned out to be the one that mattered most in 2026.

The Three Protocols, Head to Head

EtherFi (weETH) is the largest liquid restaking protocol by a wide margin. It reached an all-time-high TVL of roughly $6.8 billion, making it one of the top DeFi protocols on Ethereum by that metric. EtherFi's key differentiator is non-custodial validator key management: it uses distributed validator technology so no single party holds a complete set of validator keys, which reduces custodial risk compared to protocols that rely on centralized node operators. It also runs "Liquid," a set of yield-optimizer vaults that accept a wide range of collateral types beyond plain ETH. weETH has the deepest DeFi integration of any LRT, with major positions on Aave, Pendle, and several L2 money markets.

Renzo (ezETH) positions itself as a "Strategy Manager" rather than a plain LRT issuer. It handles operator selection and AVS allocation on the user's behalf and has expanded into non-ETH restaking through Symbiotic, plus points-and-yield products across Solana (via Jito) and other ecosystems. Renzo's TVL sits far below EtherFi's, in the range of $450 to $480 million as of mid-2026, reflecting both a smaller base and a broader industry pullback in LRT deposits since the 2024 points-farming peak. Renzo has not had a reported hack, but its aggressive multi-chain expansion adds more deployments to monitor, which is its own form of surface area.

Kelp DAO (rsETH) built its identity on accepting a wider range of input assets, including stETH, ETHx, and Frax's sfrxETH, so existing liquid staking token holders can restake without unwinding their positions first. Kelp also runs "Gain Vaults," automated yield vaults aimed partly at L2 points farming. Kelp reached roughly $2 billion in TVL before April 2026. Then, on April 18, 2026, an attacker drained 116,500 rsETH, worth about $292 million and roughly 18% of the token's circulating supply, from Kelp's LayerZero-powered cross-chain bridge. It was the largest DeFi exploit of 2026.

Image source: defillama.com/protocol/kelp

What Actually Happened to Kelp

The Kelp hack is worth understanding in detail because it is the clearest real-world lesson in this comparison. The bridge used a "1-of-1" verifier configuration for LayerZero cross-chain messages, meaning a single node's approval was enough to authorize a transfer. Attackers did not touch Kelp's smart contracts. Instead, they compromised the RPC infrastructure feeding that verifier, then launched a DDoS attack against Kelp's backup nodes to force a failover onto attacker-controlled infrastructure. With their own nodes now the sole source of truth, they fed the verifier a forged cross-chain message, and it approved the release of 116,500 rsETH.

Because Kelp's bridge held reserves backing rsETH across more than 20 networks, the damage spread instantly. Aave, SparkLend, and Fluid froze markets within hours. Aave's TVL fell from $26.4 billion to under $14 billion as the attacker used stolen rsETH as collateral to borrow against, leaving roughly $190 million in bad debt on Aave alone. Kelp and Aave completed a coordinated recovery by mid-May 2026, refilling the bridge and restoring normal rsETH operations about five weeks after the attack. Kelp also upgraded its bridge to require four independent verifier attestations instead of one and began migrating from LayerZero to Chainlink's CCIP.

Image source: docs.layerzero.network/v2/workers/off-chain/dvn-overview

Protocol Comparison

How to Evaluate Any Liquid Restaking Token Before Depositing

Before putting ETH into any LRT, check these factors rather than relying on APY alone:

• Bridge architecture, not just smart contract audits. The Kelp exploit was not a contract bug. It was an infrastructure and verifier design flaw that audits typically do not catch. Ask how many independent verifiers or attestors are required to move funds across chains, and whether that number is above one.
• Concentration of TVL relative to circulating supply. Kelp's bridge held reserves backing a large share of rsETH's total supply in one place. A protocol where a single system holds a large percentage of a token's backing is a bigger single point of failure than one with more distributed liquidity.
• Operator and validator decentralization. Look for distributed validator technology or multiple independent node operators rather than a small trusted set, since a compromised or malicious operator set introduces custodial-style risk inside a supposedly non-custodial product.
• Yield source transparency. Understand whether yield comes from base ETH staking, AVS rewards, points programs, or token incentives, since incentive-driven yield can disappear quickly when a rewards campaign ends.
• Withdrawal conditions during stress. Check whether the protocol has paused withdrawals before, and how long a recovery process took if an incident occurred. Kelp took about five weeks to fully restore rsETH operations after its hack.
• Cross-chain exposure you did not ask for. If you hold an LRT on an L2, confirm whether it is backed by native reserves or a bridged wrapped version, since bridged versions inherit the bridge's risk even if the base protocol is otherwise sound.

Best Choice by User Type

Common Mistakes Users Make With LRTs

• Chasing the highest advertised APY without checking where the yield comes from. A few extra points of yield rarely compensate for taking on a materially riskier bridge design.
• Holding a wrapped LRT on an L2 without checking backing. Users holding bridged rsETH on Arbitrum or Base during the Kelp hack had no way to know their tokens were backed by a bridge that had just been drained until Kelp and Aave coordinated a recovery.
• Treating "audited" as equivalent to "safe." Kelp's contracts were audited. The exploit came from RPC infrastructure and verifier configuration, areas most standard audits do not fully cover.
• Over-concentrating restaking exposure in one protocol. Since restaking stacks risk on top of already-staked ETH, spreading exposure across two protocols with different bridge and operator models reduces the chance that a single incident wipes out your entire restaked position.
• Ignoring recovery history. A protocol's response to an incident, including how transparently and quickly it communicated and restored funds, tells you more about future risk than a clean track record with no incidents at all, since every protocol eventually faces some kind of stress event.

Risks and Tradeoffs Across All Three

Every liquid restaking token carries smart contract risk, slashing risk from AVS misbehavior, and depeg risk if the LRT's market price diverges from its underlying ETH value during stress. Bridge risk is the differentiator right now. EtherFi and Renzo have not had a fund-loss exploit, but both use LayerZero-based bridging in some form, the same technology stack implicated in Kelp's hack, so their own verifier configurations are worth checking rather than assuming safety by association with a bigger name.

Liquidity risk also differs. EtherFi's size means weETH is easier to enter and exit at scale without moving the market. Renzo and Kelp, at a fraction of EtherFi's TVL, can see wider slippage on large trades, particularly during periods of stress when everyone wants to exit at once, which is exactly what happened to rsETH holders in April 2026.

When Liquid Restaking Makes Sense, and When It Does Not

Liquid restaking makes sense if you already plan to stake ETH long-term, understand you are adding a second layer of smart contract and slashing risk on top of base staking, and want to remain liquid for DeFi use rather than locking funds. It does not make sense if you are risk-averse, need guaranteed liquidity on a specific date, or are chasing yield primarily because of a temporary points or incentive program rather than sustainable AVS revenue.

It also does not make sense to hold a large, undiversified position in any single LRT's bridged version on an L2 you rarely check, since that is precisely the exposure that turned a protocol-level exploit into a multi-chain, multi-protocol contagion event in April 2026.

My Take

EtherFi is the strongest default choice for most users right now. It has the largest TVL, the deepest DeFi integration, and a clean security record through the period when a direct competitor suffered the largest DeFi hack of the year. That does not make EtherFi risk-free, and its LayerZero-based L2 bridging deserves the same scrutiny anyone should apply before trusting a cross-chain deployment.

Kelp DAO is not disqualified by its hack, but it needs to earn back trust. The team responded competently: it paused contracts within 46 minutes, coordinated with Aave on recovery, fully restored operations within five weeks, and moved to a four-verifier bridge model plus a CCIP migration. That is a credible response, but I would treat any new Kelp deposit as a smaller, monitored position until the new bridge architecture has a real track record, not a freshly announced one.

Renzo sits in the middle. Its multi-chain, multi-strategy approach is legitimate for advanced users comfortable tracking more moving parts, but its smaller TVL means less liquidity depth and less battle-testing than EtherFi. I would not put a first-time restaker into Renzo before they understand how its Symbiotic and cross-chain deployments actually work. Whichever protocol you choose, check the verifier count on any bridge before you check the APY.

Conclusion

The real decision in liquid restaking is no longer just about yield. EtherFi's scale and clean track record make it the reasonable default for most users; Kelp DAO's multi-asset flexibility remains useful but now carries a documented bridge-risk lesson that should shape position sizing; and Renzo fits users who specifically want managed, multi-chain restaking exposure and are willing to monitor it closely. The single biggest practical takeaway from 2026 is that bridge and verifier design matters as much as smart contract audits, and it is worth five minutes of research before any deposit. Check each protocol's current bridge security setup directly on its documentation before committing capital, since these configurations change quickly after incidents like Kelp's.

FAQs

1. Is Kelp DAO safe to use after the April 2026 hack?

Kelp completed a full technical recovery by late May 2026 and upgraded its bridge to require four independent verifiers instead of one. It is functioning normally again, but a shorter post-upgrade track record means a smaller, monitored position is more prudent than a large deposit right now.

2. Which liquid restaking token has the highest yield?

Yields shift constantly based on AVS rewards and incentive programs, and Renzo has shown higher yields at times due to more aggressive AVS strategies, but no LRT should be chosen on yield alone. Check current rates directly on each protocol's dashboard before comparing, since a temporary incentive can disappear within weeks.

3. Can I lose money holding weETH, ezETH, or rsETH even without a hack?

Yes, through slashing if a validator or AVS misbehaves, or through depeg risk if market price temporarily diverges from the underlying ETH value during stress. These risks exist independently of any single protocol's security history and apply across the category.

4. Should I hold my LRT on Ethereum mainnet or bridge it to an L2?

Holding on mainnet avoids extra bridge risk entirely, while bridged versions on L2s depend on the bridge's reserve backing and verifier security. The Kelp hack showed exactly how bridged token holders can be affected even when they never interacted with the exploited contract directly.

5. Is liquid restaking worth it compared to plain liquid staking?

Liquid restaking offers higher potential yield through AVS rewards but adds smart contract, slashing, and bridge risk layers that plain liquid staking does not carry. Users who want simpler risk exposure should compare it against pure liquid staking options rather than assuming restaking is automatically the better choice.

References

DefiLlama: https://defillama.com

CoinDesk, "2026's Biggest Crypto Exploit: Kelp DAO Hit for $292 Million With Wrapped Ether Stranded Across 20 Chains": https://www.coindesk.com/tech/2026/04/19/2026-s-biggest-crypto-exploit-kelp-dao-hit-for-usd292-million-with-wrapped-ether-stranded-across-20-chains

CoinDesk, "The $292 Million Kelp DAO Exploit Shows Why Crypto Bridges Are Still One of the Industry's Weakest Links": https://www.coindesk.com/tech/2026/04/21/the-usd292-million-kelp-dao-exploit-shows-why-crypto-bridges-are-still-one-of-the-industry-s-weakest-links

Halborn, "Explained: The Kelp DAO Hack (April 2026)": https://www.halborn.com/blog/post/explained-the-kelp-dao-hack-april-2026.

The Block, "Kelp DAO, Aave to Resume rsETH Operations as Recovery From $292 Million Exploit Progresses": https://www.theblock.co/post/401060/kelp-dao-aave-resume-rseth.

Cointelegraph, "KelpDAO Says rsETH Restored 5 Weeks After Protocol Hack": https://cointelegraph.com/news/kelpdao-says-rseth-restored-5-weeks-after-protocol-hack.

OurNetwork, "Restaking: ether.fi, Swell, and Jito": https://ournetwork.substack.com/p/on342-restaking

Aave Governance Forum, "ARFC: Onboarding weETH to Aave V3 on Scroll": https://governance.aave.com/t/arfc-onboarding-weeth-to-aave-v3-on-scroll/18301/6

War dieser Artikel hilfreich für Sie? Bitte teilen Sie uns in den Kommentaren unten mit, was Ihnen gefallen oder nicht gefallen hat.

Chanuka is a content writer, editor and contributor at Panaprium, specializing in long-form editorial articles. He conducts in-depth research and produces well-structured, carefully edited content with a strong focus on clarity, SEO best practices, and consistent formatting. His work spans lifestyle, fashion, wellness, and technical topics, and all articles are reviewed and refined to meet Panaprium’s editorial standards.