Slashing is one of the most consequential risks in proof-of-stake staking because it can destroy part of the stake itself. But the direct penalty is only part of the story. A single operational failure can also disrupt other validators, interrupt rewards and create wider financial and business losses.
This guide explains how slashing happens, introduces Lionscraft's Slashing Event Blast Radius framework, and explores the controls that help operators and institutions prevent, contain and recover from incidents.
Lionscraft has studied Ethereum slashing incidents and their financial consequences over several years, publishing annual Ethereum Slashing Reviews for 2023, 2024 and 2025. These reports provide additional context for understanding how slashing happens, how losses can spread, and what operators can do to reduce their exposure.
What slashing is
In a proof-of-stake network, validators lock up tokens as a security deposit. In return they earn rewards for proposing and confirming blocks.
If a validator breaks the network's core rules in a way that could harm it, the protocol destroys part of that deposit. This is called slashing. It happens automatically. Nobody decides it and nobody can reverse it.
On Ethereum, a validator is slashed for one of two things:
- Double proposing: signing two different blocks for the same slot.
- Contradictory voting: signing two votes (attestations) that conflict with each other.
Other proof-of-stake networks have similar rules. Some also slash for long downtime. The exact rules and percentages are set by each network, so they need to be checked chain by chain.
What actually causes it
Slashing is rarely an attack. In practice it is almost always an operational mistake, and the same few mistakes come up again and again:
- The same keys running in two places. An operator sets up a backup machine for redundancy, or moves validators to new servers, and for a moment both copies are signing. This is the most common cause by far.
- Lost or wiped slashing protection data. Validator software keeps a record of what it has signed so it never signs a conflicting message. If that record is lost during a migration, the protection is gone.
- Badly built failover. Automatic "switch to backup if the main node looks down" logic can start the backup while the main node is still running.
- Software bugs. Rare, but when many operators run the same client software, one bug can hit many validators at once.
A real example: validator migration failure in April 2023
In April 2023, 11 Ethereum validators were slashed following a migration to a new validator cluster. Keys that were believed to have been deleted from the original cluster were unexpectedly restored after a software restart, allowing validators in both clusters to sign conflicting messages.
The incident illustrates how an apparently routine infrastructure migration can cause slashing when key lifecycle management and operational safeguards fail.
The key point: slashing risk is mostly about how an operator manages keys, changes and failover. That makes it something you can assess and reduce, not just a random event.
Slashing is not the same as downtime
People often mix the two up. When a validator is simply offline, it misses rewards and pays small penalties, roughly what it would have earned in the same time. That is a cost, not a loss of the deposit.
Slashing is different: it is a penalty on the deposit itself, and the validator is forced out of the network. Good operators accept a little downtime rather than risk running a second copy of the same keys. Safety first, uptime second is the right rule.
How large can the loss be?
On Ethereum, the financial consequences of slashing begin with protocol-level penalties.
These include:
- Initial slashing penalty: A portion of a validator's effective balance is immediately deducted.
- Forced exit: A slashed validator is removed from active validation and incurs further penalties during the exit process. Withdrawal timing depends on the protocol rules and network conditions in force at the time, so the exit period should not be treated as a fixed number.
- Correlation penalty: An additional penalty determined by how much stake is slashed within the same period. Large correlated slashing events can produce substantially greater losses than isolated incidents.
The precise penalty amounts depend on Ethereum's current protocol rules, validator effective balances and the extent of correlated slashing.
But calculating these penalties alone does not capture the full financial consequences of a slashing incident.
An operator may also lose future rewards, temporarily suspend otherwise healthy validators, incur recovery costs or suffer reputational and commercial damage.
To understand this broader exposure, we need to look beyond the protocol penalties themselves.
But the protocol penalty is not necessarily the full financial loss. In our 2023 Ethereum Slashing Review, Lionscraft introduced the Slashing Event Blast Radius to account for losses beyond the initial penalty, including lost rewards, operational disruption and the impact on other validators temporarily taken offline during an incident.
In one incident we examined, 11 validators were slashed during an infrastructure migration, while approximately 1,000 additional validators were temporarily shut down as a precaution. The total estimated financial impact was approximately 18% higher than the direct slashing penalties alone.
This distinction matters for insurers and institutions: the financial impact of a slashing event may extend beyond the validators directly affected.
The Slashing Event Blast Radius
In its 2023 Ethereum Slashing Review, Lionscraft introduced the Slashing Event Blast Radius to describe how the financial impact of a slashing incident can extend beyond the validators directly slashed.
The framework identifies three layers of loss.
- Direct Slashing Penalties
- Directly Related Losses
- Indirectly Related Losses
1. Direct Slashing Penalties
These are losses imposed directly by Ethereum's slashing mechanism, including initial penalties, correlation penalties and other protocol-imposed penalties associated with the event.
They represent the immediate protocol-level financial impact.
2. Directly Related Losses
These are additional economic losses associated with the slashed validators.
They include missed attestation and proposal rewards, lost earning opportunities during forced exit, and other consequences of validators no longer participating normally in network validation.
Even after the initial penalty, the economic impact on the affected stake can continue.
3. Indirectly Related Losses
These are losses affecting validators and infrastructure beyond those originally slashed.
For example, an operator investigating a double-signing incident may need to shut down other validator clusters as a precaution.
Those validators may not have committed any slashable offence, but they can still experience missed rewards and downtime penalties.
The operational response to an incident can therefore expand its financial consequences.
A real example: April 2023
Lionscraft analysed an April 2023 slashing incident involving 11 Ethereum validators.
The analysis identified:
| Loss category | Estimated loss |
|---|---|
| Direct Slashing Penalties | 11 ETH |
| Directly Related Losses | 1.48 ETH |
| Indirectly Related Losses | 0.48 ETH |
| Total estimated financial impact | 12.96 ETH |
The indirect losses resulted from the emergency shutdown of a cluster of approximately 1,000 validators while the incident was being managed.
The total estimated financial impact was approximately 18% higher than the initial direct slashing penalty.
Source: Lionscraft, 2023 Ethereum Slashing Review, pp. 4–5. Figures reflect the protocol rules and operating conditions at the time of the incident.
Beyond the immediate financial losses
Slashing can also create consequences that are difficult to quantify.
Operators may face reduced confidence among delegators, loss of prospective institutional business, reputational damage, higher insurance costs and expenditure on incident investigation or remediation.
These effects may continue long after the immediate technical incident has been resolved.
Why the blast radius matters
The severity of a slashing event depends on more than the size of the initial penalty. It also depends on how widely the underlying failure spreads, how much infrastructure is affected and how effectively the operator can contain and recover from the incident.
For institutions and insurers, the relevant questions include:
- How much stake could be directly slashed?
- How many validators share the same infrastructure or operational dependencies?
- How many additional validators might be disrupted during the response?
- How long could the disruption last?
- What additional financial and commercial losses might follow?
Slashing risk is not only the probability of a validator being slashed. It is also the potential impact of a shared failure across the broader operation.
The controls that reduce the risk
Effective slashing risk management requires more than preventing a validator from signing conflicting messages.
It also requires limiting the consequences when something goes wrong and ensuring that operators can recover safely.
We group these controls into three areas.
Prevent slashing
Controls should reduce the likelihood of a slashable event occurring in the first place.
These include:
- Slashing protection databases that are enabled, maintained and safely transferred during migrations.
- Strict key management to prevent the same validator keys from signing independently in multiple locations.
- Doppelganger protection to detect potentially active validator instances before signing begins.
- Carefully designed failover procedures with safeguards against simultaneous signing.
- Remote signers or distributed validator technology (DVT), which can isolate signing keys or distribute signing responsibilities across multiple operators. These approaches can improve security and resilience, but do not eliminate slashing risk. Their effectiveness depends on the design, implementation and operational controls.
- Client diversity, change management, migration procedures and tested deployment runbooks.
Contain the blast radius
When an incident occurs, the priority is to prevent it from spreading.
Operators should understand which validators and infrastructure components share common dependencies and where a failure could cascade.
Relevant controls include:
- Infrastructure segmentation and isolation.
- Dependency mapping across keys, signers, clients, clusters and hosting environments.
- Monitoring and alerting to identify abnormal signing behaviour.
- Clearly defined emergency shutdown procedures.
- Incident response playbooks and escalation responsibilities.
- Tested procedures to prevent emergency actions from creating further slashing risks.
Recover and sustain operations
Not every failure can be prevented. Operators also need to recover from incidents while protecting the wider operation.
Controls include:
- Documented and tested recovery procedures.
- Safe restoration of validator operations.
- Defined recovery roles and responsibilities.
- Coordination with relevant infrastructure providers and other stakeholders.
- Financial resilience planning and appropriate risk transfer arrangements.
- Post-incident reviews and improvements to prevent recurrence.
The objective is not only to reduce the probability of a slashing event, but also to limit the blast radius and strengthen operational resilience.
Questions to ask an operator
If you are choosing, insuring or overseeing a staking operator, these questions help evaluate both the probability of slashing and the potential scale of its consequences.
- How do you ensure that the same validator keys cannot sign independently in two locations?
- How is slashing protection data maintained and transferred during migrations?
- How do failover procedures work, and what prevents simultaneous validator activity?
- Which client software, signing infrastructure and hosting environments do you use?
- What infrastructure dependencies are shared across your validator fleet?
- How many validators could be affected by a single operational failure?
- How would you contain an incident without unnecessarily disrupting unaffected validators?
- Have you experienced a slashing incident? What happened, what were the wider consequences, and what changed afterwards?
- Do you measure potential losses beyond direct slashing penalties, including missed rewards and emergency downtime?
- Are your operational security and resilience controls independently assessed against a recognised standard?
Clear, specific answers supported by operational evidence are more useful than generic claims of enterprise-grade security.
For insurers, it is also important to distinguish the total economic loss from the losses actually covered under a policy. Insurance coverage depends on its specific terms, exclusions, limits and definitions of insured events.
Standards are catching up
Slashing risk illustrates why operational security standards matter for staking infrastructure.
Technical safeguards can help prevent incidents, but operators also need consistent approaches to risk assessment, change management, incident response, business continuity and recovery.
ValOS is an open-source operational security and resilience standard for Ethereum validators, supported by the Lido ecosystem and developed with contributions from across the staking and security communities.
It provides a common framework for assessing and improving validator operations, helping operators identify risks, implement controls and build resilience.
This is especially important when considering the Slashing Event Blast Radius.
An operator should not only be able to demonstrate that safeguards exist to prevent slashing. It should also be able to explain how failures are contained, how affected services are recovered and how lessons are shared.
Lionscraft's work connects these perspectives: research into slashing incidents and economic losses, operational security frameworks such as ValOS, and risk education for insurance organisations including Munich Re.
The goal is not simply to avoid slashing. It is to build staking operations that can withstand incidents and recover safely when they occur.
Further research: Ethereum Slashing Reviews
Lionscraft publishes annual reviews examining Ethereum slashing incidents, their causes and the implications for operational risk management.
- 2023 Ethereum Slashing Review — Includes the Slashing Event Blast Radius framework and analysis of a validator migration incident.
- 2024 Ethereum Slashing Review — Annual review of Ethereum slashing activity and operational risk.
- 2025 Ethereum Slashing Review — Continuing the annual examination of slashing incidents and operational risk.
Explore the complete Lionscraft slashing research collection
Have a question about this for your organisation? A 30-minute call is the easiest way to start.
Book a scoping call