cbETH vs Kelp: staking or restaking? (2026)

Both projects offer a token linked to staked ETH on Ethereum, but the underlying activity differs. cbETH represents ETH staked through Coinbase. It is an ERC-20 token that holders can transfer while retaining exposure to staking rewards. This gives the product a relatively simple structure, with Coinbase as the centralized operator and counterparty.

Kelp is a liquid restaking protocol. Users deposit ETH or major liquid staking tokens and receive rsETH, which represents the restaked position. Restaking adds another layer of protocol and integration risk on top of ordinary Ethereum staking risk. Kelp also lists KERNEL, but its token utility is not public.

The two TVL figures are about $480.6 million for cbETH and $909.9 million for Kelp. Kelp’s larger figure does not offset the importance of its reported bridge exploit; TVL is a measure of scale, not a safety rating.

cbETH suits users who want a transferable form of ETH staked through a single, recognizable operator. Its ERC-20 format can work with Ethereum wallets and apps that support standard ERC-20 tokens. The trade-off is reliance on Coinbase for staking operations and redemptions, plus the possibility that cbETH trades away from ETH or its redemption value.

Kelp offers a different use case: liquid restaking through rsETH, with integrations across lending protocols, DEXs, wallets and other venues claimed by its homepage. That broader DeFi role may appeal to users specifically seeking restaking exposure, but it also makes the token dependent on integrations and bridge arrangements. Aave froze rsETH markets after Kelp’s April 2026 incident, illustrating how quickly DeFi utility can be affected.

If you want the simpler structure, cbETH is the clearer fit. Choose Kelp only if restaking is the goal and you are prepared to assess the incident and current status of rsETH yourself.

Neither project publishes a specific fee in the information here. Coinbase does not publish its commission on staking rewards in the cbETH material described, and Kelp’s fee structure is not stated. Kelp displays APR and APY information and a calculator, but specific live values were not captured; those figures do not establish what fees apply.

Fees outside the protocol may also matter. Swapping either token on a decentralized exchange can involve trading fees and slippage, and Ethereum transactions require network gas. Costs depend on the venue and transaction, so there is no single published total to compare.

Before using either product, check its current app and documentation for reward commissions, withdrawal terms and any transaction costs. Do not treat an advertised or estimated yield as a guaranteed return. Public sources also give different estimated cbETH reward rates depending on source and date, so no fixed rate should be assumed.

The main risk with cbETH is counterparty exposure to Coinbase. The underlying ETH is staked and held through a centralized company, and holders also face Ethereum validator and slashing risks, potential regulatory changes, and market or depeg risk. No third-party audits are listed for the token, and the project does not detail a smart-contract review here.

Kelp lists two audits and advertises a bug bounty of up to $250,000, but those measures do not remove risk. On April 18, 2026, a reported exploit of its rsETH cross-chain bridge drained roughly $290 million. Kelp and outside commentators have disputed responsibility, with discussion focused on LayerZero defaults and Kelp’s configuration. Kelp announced it would stop bridging rsETH on 20 networks, and Aave froze rsETH markets after the incident.

For Kelp, the exploit and its aftermath should weigh more heavily than the audit count. Follow official communications for recovery or compensation plans; they are not described publicly here.