Slashing is an automated penalty mechanism in proof-of-stake systems that destroys a portion of a validator's staked collateral when they commit a provably malicious act, such as signing two conflicting blocks or making contradictory attestations. It makes attacks economically self-destructive.
What Is Slashing?
2 min read
The short version
Slashing is the "break the rules and we burn your money" enforcement mechanism. It's like a security deposit that gets forfeited if you damage the apartment, except the "damage" is provably trying to cheat the network, and the forfeiture is automatic and irreversible.
How It Works
Slashing conditions are strictly defined and provable on-chain. On Ethereum, two conditions trigger slashing: (1) Double voting, attesting to two different blocks for the same slot. (2) Surround voting, making an attestation that contradicts a previous one in a way that could enable a finality attack. When slashing occurs: the validator's effective balance is reduced by at least 1/32 (~1 ETH minimum). They are forcibly exited from the validator set. A correlation penalty amplifies the slash if many validators are slashed around the same time (designed to punish coordinated attacks more severely, if 1/3 of all validators slash simultaneously, each loses their entire stake). The validator enters an exit queue and cannot withdraw remaining funds for ~36 days.
A slashing event on Ethereum
A validator operator accidentally runs two instances of the same validator key (a common misconfiguration). Both instances attest to different blocks for slot 7,500,000, a double-vote. Another validator submits a "slasher proof" to the network. The offending validator immediately loses 1 ETH (1/32 of 32 ETH) and is marked for exit. Since this was an isolated incident (not coordinated), the correlation penalty is minimal, total loss is approximately 1.5 ETH. The operator can withdraw the remaining ~30.5 ETH after the 36-day waiting period. Lesson: never run duplicate validator keys.
What People Get Wrong
You get slashed for going offline
Downtime incurs inactivity penalties (small, gradual losses) but not slashing. Slashing is reserved for provably malicious actions. A crashed node is penalized gently; a cheating node is punished severely.
Slashing takes all your stake
Minimum slash is 1/32 of your stake. Full-stake loss only happens in correlated slashing events (many validators slashed simultaneously), which indicates a coordinated attack.
Slashing can happen by accident easily
The most common accidental cause is running duplicate validator keys (two machines with the same key). Following standard setup guides and never duplicating keys prevents this entirely.
Keep Reading
Sources & Further Reading
- Ethereum Slashing Conditions
Official docs detailing when and how slashing penalties apply
- Slashing History (beaconcha.in)
Live list of all historical Ethereum slashing events with details
Questions People Also Ask
- How many validators have been slashed on Ethereum?
- As of mid-2024, approximately 400 validators have been slashed out of 900,000+ total, nearly all due to accidental key duplication, not malicious attacks.
- Can slashed validators rejoin?
- A slashed validator is permanently ejected. The operator would need to deposit a fresh 32 ETH with new keys to create a new validator.
- Do liquid staking users face slashing risk?
- Yes, indirectly. If a liquid staking protocol's node operator gets slashed, the losses are distributed across all stakers in that protocol. Reputable protocols carry insurance or slashing protection.