Kelp DAO vs Renzo: Best Liquid Restaking Token in 2026
Kelp DAO and Renzo both launched in 2024 as liquid restaking token (LRT) protocols on top of EigenLayer, providing single-token deposit interfaces (rsETH for Kelp, ezETH for Renzo) for users wanting restaking yield without managing AVS selection directly. The category as a whole faced compression in 2025-2026 alongside cooling restaking sentiment. Kelp specifically suffered a $292M exploit in early 2026 via single externally-owned admin keys with no multisig. Both protocols continue operating but with substantially different reputational positions.
Quick verdict by use case
Why Kelp DAO wins (5 reasons)
Post-incident operational hardening creates structural improvements
After the $292M exploit in early 2026, Kelp DAO implemented hardware multisig adoption, formal admin key management policies and operational practices that should prevent comparable incidents. Protocols that survive major incidents often have stronger subsequent security culture due to learned lessons. The operational improvements at Kelp post-incident are structurally meaningful even if reputational damage was real.
rsETH AVS selection has been refined since launch
Kelp's rsETH provides exposure to a curated selection of EigenLayer AVSs. The AVS selection process has been refined since launch with more emphasis on AVS quality and risk profile than during the speculative 2024 LRT race. For users wanting curated AVS exposure with active rebalancing, rsETH provides ongoing curation value.
Kelp had aggressive ecosystem partnerships during the LRT bull period
During the 2024-early-2025 LRT bull period, Kelp built ecosystem relationships across DeFi (Pendle integrations, Karak partnership, Babylon BTC restaking integrations). Some of these partnerships persist post-incident even if some have weakened. The ecosystem positioning provides distribution that newer LRTs can't easily replicate.
Lower current valuation may provide better risk-reward post-correction
Both Kelp's KEP and Renzo's REZ tokens have compressed significantly from peak valuations alongside broader LRT category compression. KEP's additional compression from the exploit incident means current valuation may price in incident risk more conservatively than Renzo's REZ. For investors comfortable with post-incident risk, KEP may offer more conservative entry points.
BTC restaking integration via Babylon provides differentiated exposure
Kelp DAO integrated with Babylon for BTC restaking, expanding beyond pure ETH LRT into BTC-based restaking products. The diversification across asset bases (ETH and BTC) is structurally broader than Renzo's ETH-focused positioning. For investors wanting LRT exposure across both major crypto assets, Kelp's positioning is more diversified.
Why Renzo wins (5 reasons)
Cleaner security record without major exploit incidents
Renzo has not experienced exploits comparable to Kelp's $292M incident. The cleaner record is structurally meaningful for risk-averse capital evaluating LRT protocol selection. While no security record guarantees future safety, the absence of major incidents reduces past-evidence-based risk concerns.
Higher TVL and broader market integration
Renzo's ezETH had been the larger LRT by TVL through much of the LRT category's growth period. Major DeFi integrations across Pendle, Morpho, Curve, Balancer, multiple chains. The broader market integration provides better composability and exit liquidity for ezETH holders. Kelp's rsETH has integrations but with somewhat narrower distribution post-incident.
More aggressive multi-chain expansion
Renzo deployed ezETH across multiple chains (Ethereum, Arbitrum, Base, Optimism, BNB Chain, Linea and others) creating broader access for cross-chain DeFi users. Kelp's multi-chain footprint is meaningful but less expansive. For users wanting LRT access from their preferred chain, Renzo's deployment is structurally broader.
Cleaner reputation for institutional capital allocation
Post-Kelp-exploit, institutional capital allocators have been more cautious about LRT protocols generally and Kelp specifically. Renzo's cleaner record makes it the structurally easier choice for institutional positioning. For DAOs, treasuries or institutional allocators evaluating LRT exposure, Renzo's positioning is more conservative.
Pufferfish ezETH peg recovery proved operational resilience
When ezETH temporarily depegged in early 2024 due to airdrop sell pressure dynamics, Renzo's operational response (clearer redemption mechanics, communication, peg recovery) demonstrated operational resilience. The depeg was a real stress test that the protocol weathered. Kelp had its own stress events but the major $292M exploit was a substantially worse incident than ezETH's temporary depeg.
Side-by-side comparison
| Dimension | Kelp DAO | Renzo |
|---|---|---|
| Architecture | EigenLayer LRT (rsETH) | EigenLayer LRT (ezETH) |
| Mainnet launch | 2024 | 2024 |
| Native token | KEP (governance) | REZ (governance) |
| LRT token | rsETH | ezETH |
| BTC restaking | Yes (via Babylon integration) | ETH-focused |
| Multi-chain deployment | Multiple chains, narrower than Renzo | Ethereum, Arbitrum, Base, Optimism, BNB, Linea |
| Major incidents | $292M exploit early 2026 | ezETH temporary depeg early 2024 |
| Post-incident response | Hardware multisig adoption, ops hardening | Operational resilience demonstrated |
| Partnerships | Karak, Babylon, Pendle (some weakened) | Pendle, Morpho, Curve, Balancer |
| Current TVL | Compressed post-incident | Larger but compressed |
| Reputational position | Working through post-exploit recovery | Cleaner record |
| Track record | 2 years (with major incident) | 2 years (without major incident) |
Scorecard
Weighted scores out of 10 across the categories that matter for production deployments.
| Category | Kelp DAO | Renzo | Note |
|---|---|---|---|
| Security record | 4.0 | 8.5 | Kelp's $292M exploit is a substantial mark against; Renzo cleaner |
| TVL / market position | 6.0 | 8.5 | Renzo's ezETH had larger market cap historically |
| Multi-chain deployment | 7.0 | 9.0 | Renzo's deployment is broader across L2s |
| Asset diversification | 8.5 | 6.5 | Kelp's BTC restaking via Babylon is broader |
| Post-incident remediation | 8.5 | 7.0 | Kelp's ops hardening post-incident is real |
| Institutional positioning | 5.5 | 8.0 | Renzo's cleaner record matters for institutional allocation |
| Composability / DeFi integration | 7.0 | 8.5 | Renzo has broader DeFi integration breadth |
| Token market liquidity | 6.5 | 7.5 | REZ has somewhat better current market liquidity |
| Reputational recovery progress | 6.0 | 8.0 | Renzo doesn't need recovery; Kelp progressing but incomplete |
| Weighted total | 6.3 | 8.0 | Edge: Renzo |
How they actually work
Kelp DAO and Renzo both provide liquid restaking token (LRT) primitives on top of EigenLayer, with similar core mechanics but different operational and integration positioning.
Kelp DAO mechanics: users deposit ETH or LSTs (stETH, etc.) and receive rsETH representing their restaked position. Kelp manages: which EigenLayer AVSs the underlying stake secures, how rebalancing across AVSs happens, how slashing risks are managed at the protocol level. rsETH holders earn yield from EigenLayer base staking plus AVS-specific rewards. KEP is the governance token for the Kelp DAO. The protocol expanded into Babylon BTC restaking integration, creating diversified asset base exposure.
Renzo mechanics: users deposit ETH or LSTs and receive ezETH representing their restaked position. Renzo manages AVS selection, rebalancing, slashing risk management. ezETH holders earn yield from EigenLayer base staking plus AVS-specific rewards. REZ is the governance token. Renzo deployed ezETH across multiple chains creating broader cross-chain access.
The core mechanism is similar between both. Differences emerge in: AVS selection curation philosophy, multi-chain deployment breadth, ecosystem partnership focus, asset base diversification plus operational practices.
Both protocols faced category-wide compression as restaking sentiment cooled in 2025-2026. Initial speculative interest in LRTs was substantial; actual AVS adoption proved slower than initial expectations created. Token prices for both KEP and REZ compressed alongside the broader LRT category.
The major differentiating event was Kelp's $292M exploit in early 2026 via single externally-owned admin keys with no multisig. The exploit was at the Kelp protocol layer rather than EigenLayer directly but caused substantial losses. Kelp responded with operational hardening including hardware multisig adoption. The reputational damage was real and persists; the operational improvements should prevent comparable future incidents.
Renzo experienced its own stress events including the ezETH temporary depeg in early 2024 due to airdrop sell pressure dynamics. The operational response demonstrated resilience: clearer redemption mechanics, transparent communication, peg recovery. While stressful, the depeg was substantially smaller than Kelp's exploit in absolute impact.
For users entering LRTs in 2026: the choice between Kelp and Renzo is largely about how you weigh past incidents. Renzo has the cleaner record. Kelp has post-incident operational improvements. Neither is obviously better than EigenLayer's direct interface for sophisticated users wanting maximum control. Or alternatives like Ether.fi or Puffer for users wanting the cleanest LRT options.
The honest assessment: both have meaningful real protocols providing legitimate LRT services. Renzo has structural reputational advantages from cleaner record. Kelp has post-incident operational improvements that may make it structurally safer going forward despite past damage. For risk-conservative LRT exposure, Renzo (or alternatives like Ether.fi) is the cleaner choice; Kelp is acceptable for users comfortable with post-incident-remediated protocols.
Tokenomics compared
KEP and REZ have similar governance-and-fee-share mechanics with different scope and current pricing.
KEP is the governance token for Kelp DAO. Token launched with allocation to early users, ecosystem participants and team. KEP holders vote on protocol parameters, AVS selection direction and ecosystem decisions. The token has compressed significantly post-exploit alongside broader LRT category compression and incident-specific reputational impact.
REZ is the governance token for Renzo. Token launched in early 2024 with airdrop to ezETH holders and early ecosystem participants. REZ holders vote on protocol parameters and ecosystem decisions. The token has compressed alongside broader LRT category but without the additional incident-specific impact that affected KEP.
For investors evaluating these as bets: both are exposed to LRT category recovery if restaking sentiment improves. Both face structural pressure from category-wide compression. KEP has additional incident-specific overhang that could create catch-up potential if Kelp's post-incident recovery succeeds. Or could persist as structural discount if recovery is slow.
The honest comparison: REZ is the more conservative LRT governance token bet. KEP is the higher-beta bet on Kelp's post-incident recovery succeeding. Different risk-reward profiles for different investor preferences.
Both tokens face the same broader question: whether LRT governance tokens capture meaningful value from the underlying restaking activity. The mechanism for value capture has been less clean for LRT governance tokens than for protocols with direct fee-to-token revenue translation. EigenLayer's EIGEN remains the more mature restaking governance token investment overall.
For builders: ignore the token comparison and pick on protocol fit. The token economics affect token price; they don't determine deployment success. For LRT users, focus on rsETH or ezETH characteristics rather than KEP or REZ governance utility.
The broader LRT category has faced compression throughout 2025-2026 as initial speculative interest cooled and actual restaking adoption proved slower than initial expectations. Recovery for both Kelp and Renzo depends on broader category recovery plus protocol-specific execution.
Security model
The security comparison between Kelp and Renzo is substantially shaped by Kelp's major 2026 exploit.
Kelp DAO security model post-incident: hardware multisig adoption, formal admin key management policies, operational hardening across protocol operations. The smart contracts have been audited; the post-incident period has reinforced operational discipline. Going forward, the operational improvements should prevent comparable single-key admin exploits.
Known concerns for Kelp: lingering reputational impact from the $292M exploit, potential discovery of additional issues during post-incident audit reviews, dependency on EigenLayer protocol stability, smart contract risks at the LRT abstraction layer.
The early 2026 admin-key exploits affected multiple Solana DeFi protocols (Drift, Wasabi) plus Kelp DAO on Ethereum. The category-wide pattern was single externally-owned admin keys with insufficient multisig protection. All affected protocols responded with operational hardening. Kelp's operational response has been substantive.
Renzo security model: smart contract audits, operational practices that have weathered stress events without major exploits. The ezETH temporary depeg in early 2024 was operationally challenging but not a security incident in the smart contract exploit sense. The protocol has demonstrated operational resilience.
Known concerns for Renzo: dependency on EigenLayer protocol stability, smart contract risks at the LRT abstraction layer, potential edge cases in multi-chain deployment coordination, oracle and price feed dependencies for ezETH peg maintenance.
Both protocols have audit programs, bug bounty programs and responsible disclosure. Both rely on EigenLayer for underlying restaking infrastructure. The honest comparison is that Renzo has the cleaner security record by a substantial margin while Kelp has post-incident remediation that may make future security stronger but comes after substantial past damage.
For risk-averse capital: Renzo is structurally safer choice. For users comfortable with post-incident-remediated protocols: Kelp's operational improvements are real even if reputational damage persists.
For absolute minimum LRT risk: consider EigenLayer direct deposits or alternatives like Ether.fi (no major incidents) or Puffer (different architectural model). Both Kelp and Renzo are reasonable but Ether.fi specifically has had cleaner overall record than either.
For users entering LRTs: don't allocate more than you can afford to lose. LRT layering adds smart contract risk on top of base staking risk on top of EigenLayer AVS risks. Verify protocol operational quality before exposing capital.
Developer and user experience
User experience differs reflecting cleaner-record protocol vs post-incident-remediated protocol positioning.
Renzo UX: standard LRT deposit and management flow. Deposit ETH or LSTs, receive ezETH, hold for yield, redeem when needed. Multi-chain deployment means users can interact from preferred chain without bridging to Ethereum mainnet. Standard EVM wallets work (MetaMask, Rabby, Coinbase Wallet). DeFi integrations (Pendle, Morpho, Curve, Balancer) provide ezETH composability for sophisticated users.
Kelp UX: similar deposit and management flow with rsETH. Multi-chain deployment is meaningful but somewhat narrower than Renzo's. Babylon BTC restaking integration provides additional asset base option. Standard EVM wallets work. DeFi integrations exist but with somewhat reduced post-incident depth.
For wallet integration: both use standard EVM wallets via their respective chain deployments. Bridge from Ethereum mainnet to L2s where needed.
For account funding: both accept ETH or major LSTs (stETH, etc.) as deposit assets. Withdrawal mechanics involve standard redemption flows with EigenLayer cooldown periods.
For DeFi composability: Renzo's broader DeFi integration provides more composable options. Kelp's integrations have been somewhat reduced post-incident but core integrations persist.
For institutional users: Renzo's cleaner record makes it the structurally easier choice for institutional procurement processes. Kelp's post-incident positioning creates additional due diligence friction for institutional allocation.
For cross-asset users wanting both ETH and BTC restaking: Kelp's Babylon integration provides combined exposure. Renzo focuses on ETH restaking.
The honest assessment: Renzo provides cleaner overall UX and broader DeFi integration. Kelp provides BTC restaking option that Renzo doesn't match. For pure ETH LRT exposure with cleanest UX, Renzo is structurally better. For diversified ETH+BTC LRT exposure, Kelp is structurally broader.
Who should pick which
LRT user wanting cleanest security record
Renzo. No major exploit incidents. Operational resilience demonstrated.
LRT user wanting BTC restaking exposure alongside ETH
Kelp DAO via Babylon integration. ETH-only LRTs don't match this scope.
Multi-chain DeFi user wanting LRT access from preferred chain
Renzo. Deployment across Ethereum, Arbitrum, Base, Optimism, BNB Chain, Linea.
Institutional capital evaluating LRT allocation
Renzo (or alternatives like Ether.fi). Kelp's post-incident positioning creates DD friction.
DeFi user wanting maximum composability with LRT
Renzo. Broader integrations with Pendle, Morpho, Curve, Balancer.
Risk-tolerant investor wanting Kelp post-incident recovery exposure
Kelp DAO via KEP. Speculative bet on operational improvements translating to recovery.
LRT-curious user wanting cleanest first experience
Neither (consider Ether.fi or direct EigenLayer instead). Both Kelp and Renzo have stress event histories.
Final verdict
Kelp DAO and Renzo both provide legitimate liquid restaking primitives but with substantially different reputational positioning after the early 2026 incident.
If you want LRT exposure with the cleaner security record and broader multi-chain deployment, Renzo is the right choice. The absence of major exploit incidents is structurally meaningful. The multi-chain ezETH deployment across Ethereum, Arbitrum, Base, Optimism, BNB Chain and Linea provides broader access. The DeFi integration breadth (Pendle, Morpho, Curve, Balancer) creates better composability. The operational resilience demonstrated through the early 2024 ezETH depeg recovery shows the protocol can weather stress.
If you want diversified LRT exposure across both ETH and BTC bases or you're comfortable with post-incident-remediated protocols, Kelp DAO is acceptable. The Babylon BTC restaking integration provides asset base diversification Renzo doesn't match. The post-incident operational hardening (hardware multisig adoption, formal admin key policies) addresses the specific failure mode that caused the $292M exploit. For users believing in Kelp's recovery thesis, the current valuation may price in incident risk conservatively.
Both protocols faced category-wide compression as restaking sentiment cooled in 2025-2026. The category as a whole hasn't recovered to peak speculation levels. Both KEP and REZ have lost substantial value from peak. Recovery depends on broader LRT category recovery plus protocol-specific execution.
The market has voted that Renzo retained more of its category position post-incident than Kelp. The reputational gap may close if Kelp executes well on post-incident recovery. Execution will need to be substantial.
The honest call: most LRT users should consider EigenLayer direct deposits or alternatives like Ether.fi for the cleanest record. Among Kelp vs Renzo specifically, Renzo is the safer default. Kelp makes sense for users specifically wanting BTC restaking via Babylon integration or believing in post-incident recovery thesis.
The TG3 client recommendation: institutional or risk-averse capital defaults to Renzo (or Ether.fi). Diversified ETH+BTC LRT users default to Kelp for the Babylon integration. For most users, the LRT category as a whole carries enough risk that allocating heavily to any single LRT (including category leaders) is questionable. Diversified LRT exposure across multiple protocols may be safer than concentration in any single one.
FAQ
What happened with Kelp's $292M exploit?
Should I use Kelp or Renzo for liquid restaking?
Are LRTs still a good category to be in?
What is rsETH versus ezETH?
Is Kelp safe to use after the exploit?
How do KEP and REZ tokens compare as investments?
Can I use both Kelp and Renzo?
Run a free Crawlux audit
See how your project ranks against the leaders in AI search and crypto SEO. No credit card. Free tier on one domain.
Run free audit →