Slashing Definition: Slashing is a penalty in proof-of-stake blockchains that destroys part of a validator’s staked coins when it provably breaks consensus rules, such as signing two conflicting blocks. The slashed validator is also forced out of the network, and the penalty grows sharply when many validators are slashed in the same period.
What Is Slashing?
A proof-of-stake network trusts its validators because each one has posted collateral. Collateral only means something if the network can take it. Slashing is the mechanism that does the taking: when a validator is caught cheating, the protocol burns part of its stake automatically, with no court, vote or appeal.
The key word is provable. Slashing does not punish bad luck or slow servers. It punishes a validator that has signed two statements which cannot both be true, because those two signatures are mathematical evidence of an attempt to split the chain. Any other validator can submit that evidence, and the protocol pays the whistleblower a small reward for doing so.
Why is signing twice so dangerous? A validator that endorses two competing versions of history could help an attacker show one version to a merchant and another to the rest of the network, the core trick behind double spending. Slashing makes that trick expensive enough that nobody profits from it.
How Does Slashing Work?
On Ethereum, three actions are slashable. A validator can propose two different blocks for the same 12-second slot, or cast two different votes for the same target, known as a double vote. Or it can cast a vote that surrounds an earlier one, which amounts to rewriting its own past position. All three leave two signatures that contradict each other.
Once evidence lands on-chain, the penalty arrives in three parts. First, an initial penalty is burned immediately; since the Pectra upgrade in May 2025, it equals 1/4,096 of the validator’s balance, down from 1/32 before. Second, the validator is locked in an exit process for about 36 days and keeps losing small amounts because it can no longer earn.
Third, around the halfway point, the protocol applies a correlation penalty based on how much total stake was slashed in the same 36-day window. That penalty equals the validator’s balance multiplied by three times the share of all stake that was slashed, capped at 100%.
The correlation penalty changes the outcome completely. A single 32 ETH validator slashed on its own pays about 0.008 ETH up front, then loses roughly 0.1 ETH in missed income during the exit period, and its correlation penalty rounds to zero.
Now suppose a bug in one popular client makes 10% of all stake sign conflicting votes in the same week. Three times 10% is 30%, so each of those validators also loses about 9.6 ETH of its 32. If a third of all stake misbehaves together, the multiplier reaches 100% and every one of those validators loses everything.
That scaling is deliberate. An isolated mistake cannot threaten the network, so the protocol treats it lightly. A coordinated fault by a large share of validators is exactly what an attack looks like, so the protocol treats it as one, whether it was malicious or not.
Slashing vs. Inactivity Penalties
| Slashing | Inactivity penalties | |
|---|---|---|
| Trigger | Signing two conflicting messages | Missing duties because the validator is offline |
| Size of loss | Small alone, up to 100% when correlated | Roughly equal to the rewards missed |
| Forced exit | Yes, the validator is removed | No, it can resume when back online |
| Who can report it | Any validator, with evidence | Applied automatically by the protocol |
| Typical cause | Duplicate keys on two machines | Server crash, network outage, maintenance |
Other networks tune the same idea differently. The Cosmos Hub slashes 5% of stake for double-signing and 0.01% for extended downtime, and it applies the loss to delegators as well as to the validator itself.
Why Is Slashing Important for Traders?
Slashing is the tail risk inside every staking yield. The chance of losing stake in any given year is small, but the loss is not proportional to how careful you are, because it depends on what the operator does with its keys.
On 10 September 2025, 39 validators run by one operator were slashed together after a maintenance mistake launched a second copy of their keys. The stakers behind them did nothing wrong. When you stake through a staking pool, you are choosing an operator’s discipline as much as a yield.
Correlation is the risk that matters for markets. A single large operator or a single dominant client software running a big share of validators turns one bug into a correlated slashing event, and the penalty scales with it. That is why a large slashing would hit liquid staking tokens first: holders would sell the token before the size of the loss was known, and the token could trade below the value of the ETH it represents.
The risk is also spreading. Restaking lets the same staked ETH secure additional services, and each service adds its own slashing conditions. Extra yield comes from accepting more ways to be slashed, which is worth pricing in before you chase it.
Key Takeaways
- Slashing destroys part of a validator’s stake when it provably signs two conflicting messages, and it forces the validator out of the network.
- Downtime is not slashable on Ethereum; it only costs roughly the rewards the validator would have earned while offline.
- Ethereum’s correlation penalty makes the loss tiny for an isolated mistake and up to 100% when a third of all stake is slashed in the same window.
- Most real slashing events come from operator error, such as running the same keys on two machines, so choosing an operator is choosing a risk.
- Liquid staking and restaking products carry slashing risk too, and a correlated event would likely hit their market price before the losses were final.
Does going offline get you slashed?
No. On Ethereum, downtime only costs a validator roughly the rewards it would have earned during the outage. Slashing is reserved for provable misbehaviour, such as signing two different blocks for the same slot.
Can delegators lose money from slashing?
On networks such as Cosmos, yes, because delegated coins are slashed together with the validator's own stake. If you stake through a pool or exchange on Ethereum, the loss is passed on to you unless the operator covers it from its own insurance fund.
Do all proof-of-stake blockchains use slashing?
No. Cardano, for example, has no slashing and relies on lost rewards to discipline stake pool operators. Networks without slashing make attacks cheaper to attempt, so they depend more on reputation and delegator choice.
What is the most common cause of slashing?
Operator error, not attacks. Most slashing events happen when the same validator keys run on two machines at once, for example during a server migration or failover, and both copies sign different messages.
