Skip to content
Blockchain LabBlockchain LabTHE VENTURE STUDIO

LibraryScaling2023Design paperCorpus record

EigenLayer: The Restaking Collective

EigenLayer. Eigen Labs.

Eigen Labs' design for letting Ethereum stakers opt in to additional slashing conditions, so new services can rent economic security instead of bootstrapping a new token set from zero.

EigenLayer's paper proposes that ether already staked to secure Ethereum can be restaked, under extra slash conditions, to secure other services the staker opts into.
Evidence
Primary paper
Re-measured
No
Assumptions
4
Records linked
7

Code

Source, repository, and what is actually hosted

  • EigenLayer white paperhttps://docs.eigenlayer.xyz/eigenlayer/overview/whitepaper
  • The source URL is not a GitHub repository. No code remote is invented.
  • Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
  • Add to a reading list

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The economic security already exists

    Ethereum validators post collateral and can be slashed for breaking Ethereum's rules. The paper asks them to accept additional rules, for additional pay, with the same collateral.

  2. Claim 02 · Paper model

    Opt-in is the whole permission system

    A staker chooses which services, called AVSs in the paper, to secure. There is no automatic claim on someone's stake by a service they did not join.

  3. Claim 03 · Paper model

    Slashing conditions are the product

    Each service defines what misbehaviour looks like and how it is proved. A vague condition is an unenforceable loan of security. The paper's safety is only as clear as those definitions.

  4. Claim 04 · Paper model

    Operators and restakers can be different people

    The capital and the machine that runs the extra software need not belong to the same party. Delegation is part of the design and part of the risk.

  5. Claim 05 · Paper model

    This is not a 2023 measurement of Ethereum

    The paper is a mechanism. How much stake opted in, and into what, is a fact that moves. Do not cite the paper as a capacity figure.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The economic security already exists

    Observation

    What the study says

    Ethereum validators post collateral and can be slashed for breaking Ethereum's rules. The paper asks them to accept additional rules, for additional pay, with the same collateral.

    Model

    What has to hold

    Stakers understand they can lose ether for failures that are not Ethereum consensus failures.

    Falsifier

    What would retire it

    How many services does this collateral already backstop?

  2. 02 Opt-in is the whole permission system

    Observation

    What the study says

    A staker chooses which services, called AVSs in the paper, to secure. There is no automatic claim on someone's stake by a service they did not join.

    Model

    What has to hold

    The extra yield compensates the extra risk. The paper does not guarantee that it does.

    Falsifier

    What would retire it

    Is the operator the same party as the staker?

  3. 03 Slashing conditions are the product

    Observation

    What the study says

    Each service defines what misbehaviour looks like and how it is proved. A vague condition is an unenforceable loan of security. The paper's safety is only as clear as those definitions.

    Model

    What has to hold

    Slashing conditions are objective enough to encode, and the proof of a fault fits in the contract.

    Falsifier

    What would retire it

    How many services does this collateral already backstop?

  4. 04 Operators and restakers can be different people

    Observation

    What the study says

    The capital and the machine that runs the extra software need not belong to the same party. Delegation is part of the design and part of the risk.

    Model

    What has to hold

    The extra yield compensates the extra risk. The paper does not guarantee that it does.

    Falsifier

    What would retire it

    Is the operator the same party as the staker?

  5. 05 This is not a 2023 measurement of Ethereum

    Observation

    What the study says

    The paper is a mechanism. How much stake opted in, and into what, is a fact that moves. Do not cite the paper as a capacity figure.

    Model

    What has to hold

    Stakers understand they can lose ether for failures that are not Ethereum consensus failures.

    Falsifier

    What would retire it

    What, exactly, gets slashed, and is that fault provable on-chain?

03 Sequence

One action, as an operating tape

  1. 01A validator, or a holder of liquid staking tokens, opts into the restaking contract and names the services they will secure.
  2. 02An operator runs the service's software and is delegated that stake, if the two roles are split.
  3. 03The service pays a fee for the security it is renting.
  4. 04If the operator breaks a stated rule, anyone able to prove it submits the proof, and the contract slashes the opted-in stake.
  5. 05The same stake remains subject to Ethereum's own slashing. The two liabilities stack.

04 Load-bearing

The argument, and where a pitch drops it

  1. Reusing collateral reuses risk

    The cut

    One pool of ether backstopping many services is capital-efficient and correlated. A bug, or a mass slash, hits the same economic base that secures the chain the services were meant to lean on. The paper has to be read as a concentration design, not only as a marketplace.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    The paper is not an audit of any particular AVS.

  2. Subjective slashing is a governance leak

    The cut

    If misbehaviour cannot be proved on-chain and a committee decides instead, the staker has trusted that committee with the collateral. The paper's crypto-economic story is strongest when the fault is objective. Services with subjective faults have changed the trust model.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    The paper is not an audit of any particular AVS.

  3. Delegation creates a new operator class

    The cut

    Restakers who do not run the software will pick operators on yield and reputation. That is a market, and it will concentrate. The design does not prevent a few operators from becoming the de facto security for many services.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    We do not describe yields. A slashing design is not a savings product.

05 Register

What has to be true

  • Cryptography · Not re-measured

    Slashing conditions are objective enough to encode, and the proof of a fault fits in the contract.

  • Stake and threshold · Not re-measured

    Stakers understand they can lose ether for failures that are not Ethereum consensus failures.

  • Model · Not re-measured

    The extra yield compensates the extra risk. The paper does not guarantee that it does.

  • Model · Not re-measured

    Ethereum itself remains the base slash. Restaking does not replace attestation duties.

06 Divergence

What happened after the paper

EigenLayer launched restaking and a set of services after the paper, with parameters, caps and operator sets that the 2023 text does not freeze. The durable idea is optional extra slash conditions on existing stake. The live book of risk is whatever stakers have actually opted into.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  5. 0 of 4 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it 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 the desk 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.

09 Lexicon

Terms, opened into the record

Restaking
Putting stake that already secures a base chain under additional slashing rules.
AVS
An actively validated service: the extra system that rents the restaked security.
Operator
The party who runs the service software, often with stake delegated by someone else.
Slashing condition
The rule that defines a punishable fault. If it is vague, the security is vague.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

Protocols

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.