EigenLayer: The Restaking Collective

The problem the paper names

A new network that needs a bond usually issues a new asset and hopes it becomes expensive to attack. EigenLayer's paper proposes that an existing staked position can take on extra duties, and extra penalties, if the holder opts in.

What the design proposes

• Restakers point stake at operators. Operators run services called AVSs in the paper's vocabulary.
• Each service defines its own slashing condition. Opting in is specific, not a blanket lien on all staked ether.
• The base staking protocol remains Ethereum's. EigenLayer is an additional opt-in layer.

How the mechanism is specified

• Security is pooled only to the extent holders accept the new penalty. Capital and risk both move.
• An operator who runs many services concentrates operational risk even if the stake is widely held.
• Withdrawal delays and veto processes, if any, are part of the risk and have to be read in the current docs as well as the paper.

What this page does not treat as proven

• Restaking does not make a service correct. It makes a defined failure expensive for those who opted in.
• The paper is not an audit of any particular AVS.
• We do not describe yields. A slashing design is not a savings product.

Why a venture studio still reads it

The question for a venture is whether it needs its own bond or whether it can state a slashing condition an existing staker could actually evaluate. If the condition cannot be evaluated, restaking is just leverage with extra steps.