LibraryCredit and stable value2023Design paperCorpus record
ether.fi: a liquid restaking and staking design with operator separation
ether.fi. ether.fi.
ether.fi publishes a flow where a staker receives a liquid claim and an operator runs the validator, with the docs drawing a line between who holds which key.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
ether.fi publishes a flow where a staker receives a liquid claim and an operator runs the validator, with the docs drawing a line between who holds which key.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 4
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.
Claim 01 · Paper model
The defect
Liquid restaking stacks three claims: the ether, the staking derivative, and a restaking assignment. Each can fail on its own.
Claim 02 · Paper model
The proposal
ether.fi publishes a flow where a staker receives a liquid claim and an operator runs the validator, with the docs drawing a line between who holds which key.
Claim 03 · Paper model
The mechanism
The staking derivative is a claim on validators the protocol selected. It is not ether.
Claim 04 · Paper model
The bound
No yield and no total value is stated here.
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.
01 The defect
Observation
What the study says
Liquid restaking stacks three claims: the ether, the staking derivative, and a restaking assignment. Each can fail on its own.
Model
What has to hold
You are reading the ether.fi contracts repository. A points blog is not the mechanism.
Falsifier
What would retire it
Which key can withdraw the ether?
02 The proposal
Observation
What the study says
ether.fi publishes a flow where a staker receives a liquid claim and an operator runs the validator, with the docs drawing a line between who holds which key.
Model
What has to hold
You are reading the ether.fi contracts repository. A points blog is not the mechanism.
Falsifier
What would retire it
Which key can withdraw the ether?
03 The mechanism
Observation
What the study says
The staking derivative is a claim on validators the protocol selected. It is not ether.
Model
What has to hold
You are reading the ether.fi contracts repository. A points blog is not the mechanism.
Falsifier
What would retire it
Which key can withdraw the ether?
04 The bound
Observation
What the study says
No yield and no total value is stated here.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
Which key can withdraw the ether?
03 Sequence
One action, as an operating tape
- 01The staking derivative is a claim on validators the protocol selected. It is not ether.
- 02Restaking, where the docs assign the position onward, adds the slashing condition of that assignment.
- 03Key separation is the part of the design that says the operator cannot unilaterally take the ether. Read the key diagram before you repeat the slogan.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
ether.fi publishes a flow where a staker receives a liquid claim and an operator runs the validator, with the docs drawing a line between who holds which key.
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
A later client, parameter or reward formula is a different object from this paragraph.
What actually moves
The cut
Restaking, where the docs assign the position onward, adds the slashing condition of that assignment.
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
A later client, parameter or reward formula is a different object from this paragraph.
What a later deployment may change
The cut
Key separation is the part of the design that says the operator cannot unilaterally take the ether. Read the key diagram before you repeat the slogan.
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
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Model · Not re-measured
You are reading the ether.fi contracts repository. A points blog is not the mechanism.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
A points programme is not the mechanism.
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
- 0 of 3 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
Liquid restaking stacks three claims: the ether, the staking derivative, and a restaking assignment. Each can fail on its own.
What the design proposes
- The staking derivative is a claim on validators the protocol selected. It is not ether.
- Restaking, where the docs assign the position onward, adds the slashing condition of that assignment.
- Key separation is the part of the design that says the operator cannot unilaterally take the ether. Read the key diagram before you repeat the slogan.
How the mechanism is specified
- The staking derivative is a claim on validators the protocol selected. It is not ether.
- Restaking, where the docs assign the position onward, adds the slashing condition of that assignment.
- Key separation is the part of the design that says the operator cannot unilaterally take the ether. Read the key diagram before you repeat the slogan.
What this page does not treat as proven
- No yield and no total value is stated here.
- This is not Lido's document. The key story differs.
- A points programme is not the mechanism.
Why the desk still reads it
ether.fi publishes a flow where a staker receives a liquid claim and an operator runs the validator, with the docs drawing a line between who holds which key.
09 Lexicon
Terms, opened into the record
- Operator key
- The key that performs validator duties. It should not be the withdrawal key. The docs either separate them or they do not.
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.
Papers
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.