RSETH: who controls it?

The control finding

Kelp restaked ETH. No issuer freeze, but its LayerZero bridge was forged on 2026-04-18 to mint ~116,500 unbacked tokens — the bridge, not the staking, was the security model that failed. Protocol rejected.

Named controller

No issuer freeze; Kelp DAO protocol and EigenLayer AVS operators control the restaked collateral

Holder’s position

rsETH represents a claim on ETH staked through Kelp and restaked to secure EigenLayer AVSs, with its exchange rate growing to reflect staking and restaking rewards.

Redemption or exit

Holders exit through Kelp's withdrawal path to ETH, subject to queue processing time, or sell rsETH on a market instead.

Dependencies an advisor should record

• Kelp DAO protocol operation and node operator set
• EigenLayer AVS operators and their slashing conditions
• Cross-chain bridge infrastructure carrying rsETH
• The withdrawal queue and its processing time
• Ethereum consensus and validator exit mechanics

Why this distinction matters

rsETH's asset-control grade is sovereign, but on 2026-04-18 its LayerZero bridge, not its staking mechanics, was compromised, minting roughly 116,500 unbacked tokens. Ketju rejected the protocol on that failure, and advisors should record bridge risk as a distinct line item from issuer freeze risk.

No single issuer or administrator has an address-level freeze function at this layer. That finding can coexist with a sound reserve, useful product, or appropriate client role. The grade prevents the on-chain wrapper from being mistaken for the absence of an administrator.

Questions before use

1. Does the exact contract and chain match the instrument reviewed here?
2. Which party can mint, burn, pause, upgrade, block, or redeem?
3. Does the client have direct redemption access or only secondary liquidity?
4. What protocol, bridge, wallet, and custodian dependencies are added?
5. Which event would force review or exit?