Skip to main content
The KelpDAO integration (public type restaking) has two forms: on Ethereum it accepts liquid staking tokens and returns rsETH; on Base, Optimism, and Arbitrum it accepts native ETH and returns a wrapped or unwrapped rsETH depending on the network.

Availability

Yield ids follow <network>-kelpdao-rseth-staking, for example ethereum-kelpdao-rseth-staking. Query GET /v1/yields?providers=kelpdao for the current listing enabled for your project.

Entering

On Ethereum, set the optional inputToken to choose between stETH, sfrxETH, and ETHx; depositing an LST requires an approval transaction ahead of the deposit, and amount has a minimum read live from the deposit pool contract. On Base, Optimism, and Arbitrum, the only input is native ETH.

Exiting

Ethereum requires an outputToken argument on exit, one of ETH, ETHx, or stETH: the withdrawal manager burns rsETH and queues the chosen asset for release once its own contract-level cooldown elapses, then a WITHDRAW pending action claims it. Both entering and exiting on Ethereum are pause-gated at the protocol level. Base, Optimism, and Arbitrum do not support exit actions: status.exit is false on these networks. The receipt token (wrsETH on Base and Optimism, rsETH on Arbitrum) stays transferable, so a position can still be moved or traded outside yield.xyz.

Rewards and position

The exchange rate between rsETH/wrsETH and the underlying asset rises as rewards accrue; rewardClaiming is automatic and there is no separate claim step for the base reward. The yield’s reward tokens also include EigenLayer Points and KelpDAO Miles, which are protocol-reported and separate from the receipt token balance.

List the live yields

Copy this request to list the KelpDAO yields enabled for your project. Yield IDs change as markets and networks are added, so query the API rather than hardcoding them.

Next steps

Restaking

Compare KelpDAO with Ether.fi and Renzo.

Action lifecycle

Build the enter and exit flow, including the outputToken argument.