WEETH: who controls it?

The control finding

ether.fi restaked ETH. No issuer freeze, but the stake is re-pledged to EigenLayer AVSs that can slash it — sovereign in custody, novel in risk. Protocol rejected; see registry.

Named controller

No issuer freeze; ether.fi protocol and EigenLayer AVS operators control the restaked collateral

Holder’s position

weETH wraps eETH, a claim on ETH staked through ether.fi and simultaneously restaked to secure EigenLayer AVSs. Its exchange rate grows to reflect both staking and restaking rewards.

Redemption or exit

Holders unwrap to eETH and use ether.fi's withdrawal queue to exit to ETH, subject to queue processing time, or sell weETH on a market instead.

Dependencies an advisor should record

• ether.fi protocol operation and node operator set
• EigenLayer AVS operators and their slashing conditions
• The withdrawal queue and its processing time
• Ethereum consensus and validator exit mechanics
• Any wrapper, bridge, or protocol built on weETH

Why this distinction matters

weETH is sovereign in custody, but the restaking layer adds a slashing surface a plain liquid staking token does not carry. Ketju's registry rejected the protocol on that risk even though the asset itself has no freeze switch, so advisors should not read 'no freeze' as 'no risk' here.

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?