COVERRACCOON
← Nexus Mutual
Product analysis · Slashing Umbrella Cover: Ether.fi ETH

Ether.fi slashing cover,
coverage and gaps.

In plain words

Catastrophe cover for ether.fi stakers against a mass slashing: only kicks in above 5,000 ETH of loss (nothing for small events) and is a private umbrella cover, not a retail product.

Ether.fi is the leading liquid restaking protocol: deposit ETH for eETH (or wrapped weETH), and it is automatically restaked through EigenLayer for extra yield and extra risk. Nexus lists an ETH Slashing Umbrella Cover for it. This is not a normal retail listing: it is private, fixed-price, and carries a 5,000 ETH deductible, so it is a catastrophe backstop against a mass slashing event, most plausibly arranged for the protocol rather than bought per user. This analysis reads the annex and checks the fit. Facts, not advice.

61/100 Limited fit

Who this is for: The ether.fi team, protecting its STAKERS (eETH/weETH holders) against catastrophic slashing

A different animal from the retail listings: private, fixed-price at 0.75% per year, with a 5,000 ETH deductible, so it pays only on a catastrophic, correlated slashing event, not routine slashing. That structure fits its target, because restaking multiplies the slashing surface: on top of Ethereum consensus slashing, EigenLayer AVS slashing is now live and can even redistribute slashed funds. Ether.fi is a top-tier, heavily audited LRT (weETH carries an A+ risk rating), which supports the covered protocol. The caveats: the attachment point is very high (nothing until 5,000 ETH, tens of millions of dollars), it is not openly purchasable, the restaking-slashing surface it insures is genuinely new and largely untested, and non-slashing LRT risks (a contract bug, an eETH discount) are not this cover. It is also the single largest exposure in the whole set.

Data confidence: medium · Assessment as of 2026-07-14 · Methodology: Raccoon Score

How to read this page: where each value comes from

On-chain Read from contracts, verifiable by anyone at any time.
Contract doc From a binding written document, off-chain but checkable.
Provider claim Stated by the provider, off-chain: a matter of trust.
Third party From a third-party source, off-chain: a matter of trust.
Our assessment Our judgement under the Raccoon methodology.

Only on-chain values are verifiable without trusting anyone. Everything off-chain, including binding documents, ultimately relies on trust in the source.

Live on-chain On-chain

Reading the chain…

Profile

Provider Nexus Mutual (see provider profile for legal nature, claims, capital) Our assessment
Product Ether.fi ETH Slashing Umbrella Cover (bespoke wording) plus a dedicated annex (read from IPFS). Private and fixed-price Contract doc
Not a retail listing Marked private in the API (isPrivate), fixed price, restricted to a set list of staking pools: an umbrella policy, not a per-user cover you can just buy On-chain
Covered protocol Ether.fi liquid restaking (eETH / weETH), auto-restaked via EigenLayer, exposed to both Ethereum consensus slashing and EigenLayer AVS slashing Provider claim
Deductible 5,000 ETH (per annex): the cover pays only for slashing losses above this, so it is catastrophe cover, not per-validator Contract doc
Price & payout asset Fixed 0.75% per year; cover and payout in ETH Provider claim
Claims assistance Per annex, Nexus Mutual and a named partner (CRS) assist the Covered Member in preparing, submitting and supporting the claim through assessor voting Contract doc

The 5,000 ETH deductible defines it: This cover does nothing until slashing losses exceed 5,000 ETH, tens of millions of dollars. Routine slashing, a validator double-signs and a few ETH are burned, is far below that line and uncovered. It is built for one scenario: a mass, correlated slashing event across Ether.fi validators or its EigenLayer AVS exposure, the kind that could actually dent the eETH backing. That is exactly the tail restaking creates: EigenLayer AVS slashing is now live, applies to every restaker delegated to a misbehaving operator, and slashed funds can even be redistributed. Read this as catastrophe reinsurance for the protocol, not per-validator insurance for a holder.

What is covered Contract doc

The umbrella cover plus annex, applied to Ether.fi. The covered event is a slashing loss, and the 5,000 ETH deductible plus the restaking layer shape where it does and does not reach.

Real-risk fit

Main risk: Catastrophic / correlated slashing above 5,000 ETH covered

The single risk most likely to hurt here is inside the cover.

2 covered 1 conditional 4 excluded ringed = main risk
Does it fit you?

Pick what you actually want protection from; the list below highlights your answer. Runs in your browser only, nothing is sent.

Even "covered" is not a payment guarantee: every claim is decided by the mutual's members (claims assessors). A risk not listed here is most likely not part of the wording at all. No advice.

Pick your risks above and only those appear here, with the verdict: covered or not.

Conditions attached Contract doc

Wording Ether.fi ETH Slashing Umbrella Cover Terms plus the annex read here from IPFS; the annex sets the 5,000 ETH deductible and the claims-assistance process
Deductible 5,000 ETH
Access Private (isPrivate) and fixed-price, restricted to pools 1, 2, 5, 22 and 23
Proof of loss Evidence-based per the annex (not a simple address signature): the Covered Member submits evidence of the slashing Covered Event, with Nexus and CRS assisting
Resubmission If a claim is declined, a further claim on the same event may be filed with additional evidence

Who decides on claims Provider claim

Same core process as every Nexus claim (Claims Committee, assessor voting), but the annex adds structure: Nexus Mutual and a named partner (CRS) assist the Covered Member in identifying the covered event, sizing the loss, preparing the claim and supporting the assessor vote, and a declined claim can be resubmitted with more evidence. No Ether.fi slashing claim is on record, and a mass-slashing loss assessment would be complex.

Raccoon Score Our assessment

A structured assessment across seven categories, 0 to 100 points in total. The score is an opinion based on the sources below, not a probability of payout and not a guarantee.

Note: this product is bought by a protocol team, not by end users. We therefore score it with our team rubric, which asks the questions a team asks. The most important one: if disaster strikes, does the money actually reach the users? Compare this score only with other team products, not with the retail list.

Premium cross-check
Raccoon Score 61/100 Limited fit
vs
Market premium 0.75%/yr low risk · snapshot
The market prices it cheaper than the rating suggests. The premium mainly measures how likely a claim is, not how good the cover is.

The premium is the underwriters price verdict: mainly how likely a claim is. The Raccoon Score measures how good the cover is: fit, clarity, capital, claims. Where they diverge, look twice.

Coverage clarity & scope control 13/20

The covered event (slashing) is well defined, the umbrella structure fits a protocol-level catastrophe backstop, and the annex (public, a plus) fixes the 5,000 ETH deductible. Deductions: nothing pays for the common small-slashing case, and non-slashing LRT risks (contract bug, eETH discount) are out.

Capital & payout capacity 15/20

Same shared pool as the provider profile, on-chain verifiable, live above. Note this is the single largest active cover in the set, so a payout would be an unusually large single draw on the pool.

Claims process & incident fit 11/15

Provider process applies, and the annex adds exactly what an incident needs: explicit claims assistance (Nexus plus CRS) and a resubmission right. Minus: untested, a mass-slashing loss across the restaking stack (LRT, EigenLayer, AVSs) is complex to assess, and AVS slashing at scale has no precedent.

User outcome 7/15

The builder question: does the payout reach the stakers? The umbrella exists to backstop staker losses, and ether.fi also runs its own insurance fund, which speaks for intent. But unlike Native Protocol Cover (clause 10.12 trustee duty) no public pass-through obligation was verifiable: the full umbrella terms are private, so the commitment to stakers rests on trust in the team.

Governance & conflicts 5/10

Nexus side unchanged. Ether.fi side: the slashing risk depends on operator behaviour and on which AVSs the protocol delegates to, both curated by Ether.fi. Reasonable but real discretion sits behind the covered risk.

Legal enforceability (inherited) 3/10

Discretionary cover, no enforceable claim: still assessor-decided, even with the annex assistance. Identical in substance to the provider profile.

Transparency to users 7/10

Better than most team products: the annex is public, the listing and its active cover are visible via the Nexus API, and ether.fi itself is heavily analysed in public. Reduced because the full umbrella terms and the exact cover-holder arrangements are private: a staker can see THAT cover exists, not exactly what it promises them.

Total 61/100 · Limited fit

Red flags Our assessment

01

Payout remains discretionary: even with the annex claims assistance, the loss is decided by assessor voting, so the provider-level warning still applies.

02

Very high attachment: nothing pays until slashing losses exceed 5,000 ETH. The everyday small-slashing case is entirely uncovered; this is catastrophe cover only.

03

Not retail: the cover is private and fixed-price, most plausibly a protocol-level umbrella. An individual eETH holder should not assume it protects them directly.

04

Novel, untested risk: EigenLayer AVS slashing is newly live, stacks the LRT plus EigenLayer plus every AVS, and slashed funds can now be redistributed. The exact size of a worst case is not yet known.

05

Largest single exposure in the set: this one umbrella is a big share of all Nexus liability, so a payout and the accumulation it represents would stress the shared pool more than any other single cover here.

06

One shared capital pool backs all Nexus products: the same event that breaches 5,000 ETH of slashing could coincide with broad market stress that also hits the pool.

Open questions Our assessment

Points this analysis could not verify. Anyone buying significant cover should clarify these first.

  • Who is the cover-holder? A private umbrella at this size is most plausibly arranged by or for Ether.fi itself; the API does not name the buyer.
  • What exactly is a Covered Event under the base Umbrella Cover terms: only Ethereum consensus slashing, only EigenLayer AVS slashing, or both, and how is an inactivity leak treated? We read the annex, not the full base wording.
  • How is the loss measured and the 5,000 ETH deductible applied across many validators and AVSs at once, and over what window?
  • Who are the managers behind the several pools carrying this cover (live above), and can they truly absorb a claim of this size? The pool IDs are public, the mandates behind them are not.

Sources

Analysis as of 2026-07-14. Live figures update every 5 minutes from the contracts. Not affiliated with Slashing Umbrella Cover: Ether.fi ETH. Informational only, no legal, investment or insurance advice.

COVERRACCOON

Independent analysis of DeFi cover. We read the terms nobody else opens.