Kelp DAO is an Ethereum Liquid Restaking Protocol Built Around rsETH

Kelp DAO is a way to keep staked ETH usable while it supports added network security, built as an Ethereum liquid restaking protocol. Depositors receive rsETH, an ERC-20 token whose exchange rate reflects pooled staking and restaking value, then use that token in compatible DeFi markets. The trade-off is layered exposure to Kelp contracts, EigenLayer, the deposited asset, and any DeFi venue.

The protocol remains operational on Ethereum mainnet. Its interface presents ETH, Lido’s stETH, and Stader’s ETHx as deposit assets, while the same screen separates restake, unstake, and withdraw into distinct actions. That distinction matters when planning liquidity.

Minting rsETH From a Wallet, Step by Step

Minting rsETH starts with an Ethereum wallet, a supported asset, and enough ETH for gas, then ends when the rsETH balance appears at the confirmed exchange rate.

1. Switch the wallet to Ethereum mainnet, which uses chain ID 1, and connect through a self-custody interface such as MetaMask or Rabby.
2. Select native ETH, stETH, or ETHx. The interface exposes three deposit choices, each valued against the protocol’s rsETH exchange rate.
3. Enter the amount and read the quoted rsETH output. An stETH or ETHx deposit first needs an ERC-20 allowance if the wallet hasn’t granted one.
4. Sign the required transactions. Native ETH goes directly to the deposit interaction, while a first token deposit uses two transactions: approval, then restaking.
5. After confirmation, inspect the transaction and rsETH balance. Adding the verified Ethereum token contract to the wallet affects display only, not ownership.

The sequence preserves self-custody at the wallet level while moving the deposited asset into a protocol-controlled smart-contract system.

The rsETH Receipt And Exchange-Rate Model

The rsETH token represents a proportional claim on ETH-denominated assets managed through Kelp, while the protocol exchange rate determines minting and redemption rather than promising a one-to-one market price.

Kelp’s LRTDepositPool accepts the asset, and its oracle logic values that deposit in ETH terms before calculating the rsETH amount. The accounting relationship uses the value of managed assets against rsETH supply, so staking rewards, restaking rewards, fees, and losses feed into backing per token. A decentralized exchange creates a separate market price from pool reserves and trading flow. Those two values can diverge during active trading. rsETH follows ERC-20 and uses 18 decimal places, so one whole token maps to 10^18 base units. Small calculations therefore round at the base-unit level.

The wallet balance records token units; the exchange rate records how much managed value those units represent.

The Risk Stack Starts Before DeFi

The Kelp DAO risk stack combines Ethereum staking, liquid-staking assets, EigenLayer restaking, upgradeable Kelp contracts, oracle accounting, and any external DeFi position built with rsETH.

Risk by Layer

Each layer changes the holder’s claim. Separating them shows users where a loss, delay, or repricing would originate before a high displayed reward obscures the underlying dependency chain.

Base Staking And LST Exposure

Native Ethereum validators post 32 ETH, and protocol-level penalties reduce the underlying staking value when validator duties fail. An stETH deposit also relies on Lido’s rebasing token and validator set, while ETHx adds Stader’s contracts and exchange-rate model. Kelp pools these assets rather than erasing their original dependencies. Ethereum itself advances in 12-second slots, groups 32 slots into one epoch, and completes an epoch in about 6.4 minutes. Those constants describe chain timing, not a guaranteed Kelp withdrawal time or a fixed reward rate.

Kelp, EigenLayer, And DeFi Exposure

In that setup, Kelp adds deposit, oracle, delegation, upgrade, pause, and withdrawal contracts. EigenLayer adds operator and Actively Validated Service economics, including slashing conditions. Supplying rsETH to Aave or another lending market adds collateral parameters, oracle behavior, interest, and liquidation. Pairing it on Balancer or Curve adds pool imbalance and price impact. The layers compound because one rsETH position can touch several systems simultaneously.

Leverage magnifies every exchange-rate move, so collateral buffers matter before another protocol enters the position.

Governance Controls And Mainnet Boundaries

In the simplest case, Kelp’s mainnet control model places contract upgrades behind a Safe multisignature and a timelock, while pause roles and circuit breakers limit specific operations during abnormal accounting conditions.

Protocol materials state that upgrades require 6 of 8 Safe signers and pass through a 10-day timelock. That delay creates an observation window for scheduled code changes. The published Ethereum registry separates LRTConfig, LRTDepositPool, LRTOracle, FeeReceiver, LRTWithdrawalManager, and the rsETH token, so authority and accounting don’t sit in one function.

Independent reviews from Sigma Prime, Code4rena, and MixBytes cover versions of the smart-contract system. Three named review providers offer useful evidence, yet an audit applies to defined code and assumptions. Upgrades, oracle inputs, EigenLayer changes, and connected DeFi markets remain separate parts of the security model.

Where rsETH Works Across DeFi

rsETH turns a pooled restaking position into an ERC-20 asset that users hold, swap, supply as collateral, pair in liquidity pools, or place into yield strategies.

That portability is the product’s main benefit. Every additional placement also adds another contract and market to the position, as described in Kelp DAO walkthrough.

Holding, Trading, And Collateral

A wallet can hold or transfer rsETH with standard ERC-20 tooling. Balancer, Curve, and Uniswap pools give traders a route between rsETH and assets such as WETH, with execution set by reserves, route size, and gas. Pendle separates principal and future yield into different tokens for markets that list rsETH-derived positions. That structure suits users who understand maturity dates and the difference between Principal Tokens and Yield Tokens; it isn’t the same as passively holding rsETH.

Lending markets add a different use. Aave, Fluid, and Compound have listed rsETH-related opportunities in Kelp’s DeFi interface, letting users supply collateral or access liquidity where a market remains enabled. The borrow limit, liquidation threshold, oracle, and available liquidity belong to that specific market. They don’t come from the ERC-20 token itself.

Do Restaking Rewards Stay Liquid?

Restaking rewards remain economically represented while rsETH stays transferable, but the token doesn’t guarantee a fixed APR or force every reward into a continuously growing wallet balance. Underlying Ethereum staking, EigenLayer rewards, protocol fees, and any separate DeFi incentives follow different accounting and distribution paths. Kelp’s exchange rate connects managed asset value to rsETH supply, while an AMM sets the tradable price. Kernel Points or other campaign units measure program participation under their own rules; they aren’t the same unit as ETH yield. Liquidity comes from rsETH transferability and active markets, not from a fixed redemption price.

Exiting Through Unstake, Withdraw, Or a Market Swap

An rsETH holder exits by requesting an on-chain unstake and later withdrawing the available asset, or by swapping through a DeFi pool for immediate market liquidity.

Even so, Kelp’s interface separates Unstake from Withdraw because a request and its final asset transfer represent different state changes. The protocol route follows withdrawal-manager processing and available underlying assets. A normal Ethereum transaction confirmation doesn’t erase that queue. Under ordinary chain operation, finality arrives after about two epochs, or roughly 12.8 minutes, while the withdrawal path follows its own readiness state.

A market swap avoids the protocol queue but accepts the pool’s price, fee, and price impact. The relevant amount comes from pool depth, trade size, routing, and Ethereum gas at execution. Existing token allowance changes whether the wallet signs one swap transaction or an approval plus the swap. Immediate liquidity therefore carries market execution terms rather than protocol redemption terms.

Four Entry Routes And Their Security Stacks

Four common paths reach rsETH, and each adds a different security stack before the holder even supplies the token to a lending market or liquidity pool.

The native mint route starts with Ethereum and Kelp, while liquid-staking-token routes inherit an upstream protocol before Kelp and EigenLayer enter. Buying rsETH adds exchange execution, pool liquidity, and token allowance behavior instead of a direct Kelp deposit.

The shortest visible transaction path isn’t automatically the narrowest dependency set; the deposited asset decides which upstream staking system remains underneath rsETH.

Network Consolidation And Legacy rsETH Recovery

More broadly, Kelp’s network policy now distinguishes normal supported routes from sunset-network recovery, so a wallet’s chain matters as much as the token symbol shown beside its balance.

For a regular user, Kelp retired bridging on 21 named networks after June 15, 2026, with recovery available through June 15, 2027. The 12-month process covers qualifying balances held directly at the cutoff. An EVM holder converts wrsETH to rsETH where required, burns that rsETH on the source chain, pays a flat 100 USDC per address on Ethereum mainnet, and receives equivalent mainnet rsETH after verification. Settlements run once per quarter, creating four scheduled processing points in a full year. Movement uses a separate address-verification sequence because it isn’t an EVM network.

Ethereum mainnet remains the backing and settlement center, while supported DeFi routes shown by Kelp include Ethereum, Arbitrum, and Base.

Kelp DAO Alternatives by Custody And Token Design

Said differently, Kelp DAO competes with EtherFi’s weETH, Renzo’s ezETH, and Puffer’s pufETH, while direct EigenLayer restaking remains the non-tokenized route for users who prefer fewer DeFi wrappers.

EtherFi’s weETH wraps eETH for DeFi and uses a native-restaking backing model. Renzo’s ezETH is a reward-bearing token whose value rises relative to its underlying assets as rewards accrue. Puffer’s pufETH connects liquid restaking with Puffer’s native validator-oriented protocol. Each alternative selects operators, handles rewards, governs upgrades, and supports withdrawals through its own contracts, so identical ETH exposure doesn’t create identical protocol exposure (set out in practice ).

Direct EigenLayer participation removes an LRT issuer and receipt-token market, yet it gives up the same style of transferable DeFi asset. Holding Lido stETH or Stader ETHx without restaking keeps base liquid staking exposure and omits the added EigenLayer layer. The decisive choice is which operator, oracle, governance, withdrawal, and liquidity dependencies match the intended use.

What readers ask about Kelp DAO