> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/security/security-and-risks/slashing-risk.md).

# Slashing Risk

Slashing is a penalty Ethereum takes out of a validator's staked ETH when the validator breaks the rules. [ether.fi](http://ether.fi) runs one of the largest validator sets on Ethereum, so it is worth being clear about how that penalty works, how much is at risk, and what ether.fi does to avoid it.

ether.fi no longer restakes ETH through EigenLayer, so EigenLayer slashing does not apply. The only slashing risk is at the Ethereum validator level.

### Ethereum validator slashing

Ethereum penalizes a validator when it provably breaks the rules, mainly by signing two conflicting blocks or votes. The validator pays an upfront penalty, is removed from staking, and pays a further penalty that grows if many validators are slashed in the same short window.

The upfront penalty is small. After the Pectra upgrade in May 2025 it dropped to one part in 4,096 of the validator's balance, which is about 0.008 ETH for a 32 ETH validator. Before Pectra it was about 1 ETH. The added penalty for correlated slashing only becomes significant if a large share of the whole network is slashed at the same time, which has never happened.

### ether.fi's record

**No ether.fi validator has been slashed since the protocol launched.** That record reflects deliberate operational work: ether.fi stakes through a curated set of professional operators that run different software and infrastructure, which keeps the chance of a shared fault low.

ether.fi has [partnered with Nexus Mutual](https://nexusmutual.io/blog/a-new-layer-of-protection-for-ether.fi) to provide the **largest ETH slashing cover in crypto history: up to 15,000 ETH** in validator slashing penalties, protecting one of the largest validator sets on Ethereum.

### How much is at risk

<table><thead><tr><th width="121.955810546875">Where</th><th>What triggers it</th><th>Most that can be lost</th><th>Today</th><th>Backstop</th></tr></thead><tbody><tr><td>Ethereum validator</td><td>Signing conflicting blocks or votes</td><td>About 0.008 ETH per 32 ETH validator; more only in a network-wide event</td><td>Spread across diverse operators; never slashed</td><td>Nexus Mutual's ETH Slashing Umbrella Cover, up to 15,000 ETH</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://etherfi.gitbook.io/etherfi/security/security-and-risks/slashing-risk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.