EigenLayer

Problem

New networks — oracles, bridges, data availability layers — each need their own validator set and their own token to pay for security. Bootstrapping that is expensive and produces weak, thinly-staked networks in the meantime.

Solution

EigenLayer lets already-staked ETH be re-pledged to secure additional services (AVSs). Operators opt in, accept extra slashing conditions, and earn extra fees. Security is rented rather than rebuilt.

Team & backers

Founded by Sreeram Kannan, a University of Washington professor, with a public and credentialed research team. Backing includes a16z crypto and Polychain. This is the opposite of the pseudonymous profile — identifiable people, institutional investors, and therefore institutional unlock schedules.

Tokenomics

EIGEN has a large investor and team allocation with multi-year vesting, meaning ongoing scheduled supply increase independent of protocol usage. Airdrop distribution drew criticism for geographic exclusions and initial non-transferability.

Risk flags

• Correlated slashing risk across AVSs
• Large investor allocation with long unlock tail
• Slashing in production is still lightly battle-tested
• Yield depends on AVS demand that has not yet materialised at scale

Verdict & notes

The technical idea is sound and the team is real. Our caution stamp is about a specific unresolved question, not about legitimacy.

Restaking concentrates risk in the same collateral pool. If several AVSs slash under correlated conditions — a shared oracle failure, a coordinated exploit — losses stack against one pool of ETH. That scenario has been modelled in research but not observed under stress in production.

The second issue is demand-side. Restaking supply arrived well ahead of AVSs willing to pay real fees for it. Until fee revenue from services justifies the risk operators take on, the yield story leans on token emissions rather than on payment for security.

What we checked: the AVS registry and live operator set, published slashing parameters, the unlock schedule from public documentation.

What we could not verify: real fee revenue per AVS, which is not consistently disclosed.