Kelpdao is a Liquid Restaking Protocol for Ethereum
Kelpdao is a protocol for keeping restaked Ether usable: restaking reuses staked assets for extra network security, while rsETH is the transferable receipt. Users deposit ETH or eligible liquid staking tokens, receive rsETH at the protocol exchange rate, and retain access to DeFi while the backing participates through EigenLayer. That design combines staking rewards, restaking rewards, and liquidity, with added exposure to smart contracts, operator selection, oracle accounting, and secondary-market pricing.
Keeping a restaked ETH position liquid for DeFi
A stETH holder who wants DeFi access while adding restaking exposure uses rsETH as the movable asset representing the resulting pooled position.
Suppose the position needs to serve as collateral on Aave next week, yet the owner still wants staking and EigenLayer rewards to remain embedded in the position. Depositing Lido's stETH or Stader's ETHx into Kelpdao mints an ERC-20 rsETH balance. That token moves between compatible contracts, trades in pools, or sits in a wallet while the protocol manages the deposited backing. Its balance uses 18 decimal places, so one whole token equals 10^18 base units. The economic value comes from the exchange rate, not from a guarantee rsETH will trade at the same price as ETH on every venue.
Withdrawal fees and time define the exit path
Kelpdao offers two protocol redemption routes on Ethereum: an instant path priced at 0.2%, and a standard path priced at 0%.
The instant route settles in under 2 minutes when its liquidity is available. The standard route takes 15–21 days because assets must move through the withdrawal process before settlement. Those figures describe protocol redemption, not a decentralized exchange sale. A swap through Balancer, Curve, or Uniswap settles with the transaction, but its outcome reflects pool liquidity, price impact, swap fees, and Ethereum gas. Gas is measured in gwei, where 1 gwei equals 0.000000001 ETH, and the sender pays it separately. Exit planning therefore starts with speed, then compares the fee and market quote.
A 0.2% charge equals 2 units per 1,000 redeemed; the same percentage applies regardless of ETH's market price.
How does rsETH turn deposits into a liquid position?
rsETH converts supported ETH-denominated deposits into transferable shares whose protocol exchange rate tracks backing, staking rewards, restaking rewards, and protocol charges. The same ground is retraced in practice.
Native ETH enters the deposit pool directly. stETH from Lido and ETHx from Stader arrive as ERC-20 tokens after an allowance authorizes the pool. The oracle expresses each supported asset in ETH terms, then divides the pool's accounted ETH value by rsETH supply. A deposit therefore mints shares at the prevailing protocol rate, rather than a fixed 1:1 amount. Node Delegator contracts allocate backing into EigenLayer strategies and selected operators. Rewards increase the value represented by each rsETH unit, while a slashing loss or accounting reduction moves the rate in the opposite direction. The holder's token count stays separate from that changing value.
Chainlink price feeds support parts of the asset-pricing system, while OpenZeppelin components provide familiar ERC-20 and access-control building blocks. EigenLayer supplies the restaking layer; Kelpdao supplies pooled asset selection, delegation, accounting, redemption, and rsETH issuance. This layered workflow removes individual operator management from the holder's daily tasks, but it also joins several contracts and governance decisions into one position.
Starting with ETH, stETH, or ETHx
The entry path starts with one supported asset - ETH, Lido stETH, or Stader ETHx - and enough ETH to pay network gas on the selected chain. On Ethereum mainnet, chain ID 1 distinguishes the network from similarly named wallet entries and test environments.
A native ETH deposit combines the asset and gas in one transaction. A conventional LST deposit needs two on-chain actions when no allowance exists: approve the Kelpdao pool, then submit the deposit. MetaMask and Trust Wallet support the connection flow; each displays the contract call and gas estimate before signature.
A short decision checklist keeps the root choice tied to the position you actually want:
- Choose ETH when you do not already hold an eligible LST.
- Choose stETH or ETHx when preserving the existing liquid-staking leg matters.
- Use Ethereum when protocol redemption into ETH, stETH, or ETHx is the planned exit.
- Budget for 2 transactions if an LST allowance has not been granted.
- Keep additional ETH outside the deposit amount for approval, mint, DeFi, and withdrawal gas.
After confirmation, rsETH appears as an 18-decimal ERC-20 balance. The receipt identifies the claim, while the portfolio view reports its protocol value and reward-related information. The next decision is whether to hold the receipt or place it in another DeFi contract.
DeFi utility adds a second layer of decisions
rsETH gains practical utility when a compatible DeFi protocol accepts it for lending, borrowing, liquidity provision, fixed-yield trading, or ordinary swaps.
Aave treats supported rsETH markets as collateral and lending assets under market-specific parameters. Balancer and Curve pair rsETH with ETH-linked assets, while Uniswap provides permissionless pools whose fee tier and reserves define execution. Pendle separates a yield-bearing position into principal and yield components with fixed expiry dates. Each route changes the dependency. Holding rsETH depends mainly on Kelpdao, EigenLayer, and the backing assets. Supplying it to Aave adds lending-market liquidation rules. A liquidity position adds automated market maker pricing and impermanent loss. A Pendle position adds maturity mechanics alongside the original token stack.
What risks sit behind a transferable restaking token?
rsETH concentrates five linked exposures in one position: backing assets, Kelpdao contracts, EigenLayer delegation, oracle accounting, and external DeFi or bridge infrastructure.
stETH and ETHx bring their own liquid-staking mechanics before restaking begins. EigenLayer introduces operator performance and slashing conditions. Kelpdao adds pooled strategy selection, exchange-rate calculation, redemption liquidity, privileged roles, and upgradeable contracts. A secondary-market discount creates depeg risk even when protocol accounting has not changed, because a pool only clears at prices its reserves support. Cross-chain rsETH adds a wrapper and messaging dependency beyond Ethereum mainnet. The token also includes a per-address 24-hour transfer-hold capability, with designated integrations eligible for exemption, so transfer behavior belongs in the position's dependency map.
Protocol upgrades use a 6-of-8 signer threshold and a 10-day timelock, placing two explicit checks between a proposed change and execution. Sigma Prime, Code4rena, MixBytes, and Bailsec have reviewed different contract scopes. An audit narrows uncertainty around reviewed code; it does not remove oracle, governance, operator, liquidity, or integration risk outside that scope.
Kelpdao within EigenLayer and the KernelDAO ecosystem
Next to that, Kelpdao is the Ethereum liquid-restaking product inside KernelDAO's three-part ecosystem, alongside Kernel restaking infrastructure and Gain vault products for managed strategies.
The unified governance asset is KERNEL, an ERC-20 token with a maximum supply of 1,000,000,000. Its published allocation assigns 55% to community rewards and airdrops, split into 20% for airdrops and 35% for future rewards. Private-sale participants receive 20%, the team and advisers receive 20%, and ecosystem partners receive 5%; together, those categories equal 100%. KERNEL is separate from rsETH: the first coordinates governance and ecosystem incentives, while the second represents an ETH-denominated restaking position. The distinction matters because holding rsETH does not require treating governance-token performance as part of the receipt's backing calculation.
EtherFi, Renzo, Puffer, and direct EigenLayer restaking
The closest alternatives differ on custody workflow, operator selection, reward accounting, DeFi reach, redemption design, and the extra contracts added above EigenLayer.
EtherFi issues eETH and wrapped weETH, Renzo issues ezETH, and Puffer Finance issues pufETH around their respective staking and restaking systems. The next part of this is set out in Kelpdao availability use cases.
weETH uses a non-rebasing wrapper around eETH and suits integrations built around that exchange-rate form. ezETH represents Renzo's managed restaking strategy and operator set. pufETH links Puffer Finance's native liquid staking design with restaking exposure. Direct EigenLayer restaking removes the liquid receipt from the middle, leaving the user to manage eligible assets, delegation, and withdrawals without rsETH. Native solo validation also starts at Ethereum's 32 ETH activation balance, a very different workflow from depositing an LST. Kelpdao fits when one pooled rsETH balance, established DeFi integrations, and the documented two-route redemption process matter more than selecting every operator personally.
That trade-off is clearest against direct EigenLayer restaking and its separate delegation workflow.
Practical questions about Kelpdao
Does rsETH rebase in the holder's wallet?
No, rsETH uses an exchange-rate design rather than adding tokens to the wallet balance. Staking and restaking rewards feed the value represented by each rsETH unit through protocol accounting. A holder therefore tracks both token quantity and the rsETH-to-ETH rate. Secondary-market quotes still differ from the protocol rate because exchange liquidity and price impact set the executable price.
Why does the rsETH exchange rate differ from one ETH?
The rsETH exchange rate reflects the ETH value of supported backing and accrued rewards divided by rsETH supply. Deposits mint at that protocol rate, so rsETH is not permanently fixed to a one-token-for-one-ETH count. Oracle updates, protocol commissions, slashing adjustments, and backing changes affect accounting, while decentralized exchange reserves determine the separate price available for an immediate swap.
Can ETH pay the gas fee for an rsETH transaction?
Yes, ETH pays gas for rsETH transactions on Ethereum mainnet. The rsETH amount being transferred does not cover the network charge automatically, so the sending address needs a separate ETH balance. Approval, deposit, DeFi placement, and redemption are distinct contract interactions, and each submitted transaction consumes gas based on its computation and the prevailing Ethereum fee market.
How are EigenLayer programmatic rewards allocated to rsETH positions?
EigenLayer programmatic rewards are allocated through periodic position accounting and a Merkle-based claim process operated by Kelpdao. The protocol identifies eligible rsETH exposure, including supported DeFi positions, for each 7-day reward cycle and assigns the relevant EIGEN amount proportionally. Eligibility rules belong to the reward program, so moving rsETH into an unsupported integration changes whether that position appears in the allocation.
Are Kelp Miles and KERNEL the same asset?
No, Kelp Miles and KERNEL serve different roles: Kelp Miles record campaign participation, while KERNEL is the unified ERC-20 governance token for KernelDAO products. Campaign rules govern any conversion or eligibility relationship between them. KERNEL has transferable token ownership, a capped supply, and governance utility, so a points entry and a KERNEL wallet balance are not interchangeable accounting records.
Who selects operators and services for rsETH?
The Risk Committee recommends operators and services, while protocol governance implements the approved set used by rsETH. Node Delegator contracts then allocate assets among selected EigenLayer operators and strategies. This pooled approach removes individual operator choice from the ordinary rsETH workflow, so operator performance, delegation policy, and governance decisions remain part of the token's underlying exposure.