# Why Ketju rejected EigenCloud (EigenLayer)

- URL: https://riadefi.com/rejections/eigencloud/
- Exposure: ETH staking
- Memo version: v1
- Reviewed: 2026-08-19
- Next review: 2026-11-19

## The memo

REJECTED ON UNCONFIRMED CONTROL AUTHORITY AND CORRELATED SLASHING COMPLEXITY. EigenCloud (the June 2025 rebrand of EigenLayer, folding in EigenDA, EigenCompute, EigenAI, and EigenVerify under one platform) lets a client directly deposit ETH or liquid staking tokens to extend Ethereum's economic security to third-party services called Actively Validated Services, earning additional yield while accepting slashing risk correlated across whatever AVSs they delegate to. Slashing went live on mainnet 2025-04-17, meaning restaking now carries a real, enforced economic penalty rather than a theoretical one. That is exactly why the open questions here matter: this review could not confirm whether a pause or emergency-veto authority exists over the restaking and withdrawal contracts, nor find any protocol-level dispute-resolution mechanism for a contested slashing event — a real gap for a system now distributing slashing authority across more than 190 independently-operated AVS teams. The EIGEN token itself carries geo-blocking, sole-discretion eligibility terms, and multi-year lockups on certain allocations.

## What would reopen the file

- Pause, veto, or emergency authority over the restaking and withdrawal contracts is publicly disclosed, including who holds it
- A protocol-level dispute-resolution mechanism for contested slashing events is documented
- EIGEN token transferability and geo-eligibility terms are confirmed current and unrestricted for this registry's client base
- AVS-level slashing incident history is independently tracked and shows no material undisclosed loss event

---

Published by Ketju Research (https://ketjuresearch.com). Educational analysis only; not legal, tax, compliance, or investment advice.
Machine-readable index: https://riadefi.com/llms.txt · Content API: https://riadefi.com/content.json