Skip to content

Slashing

What slashing is on Ethereum: the penalty that destroys part of a validator's stake for provable violations like double-signing, and why it exists as a deterrent rather than a routine risk.

Slashing is a penalty, enforced automatically by the protocol, that destroys part of a validator’s staked ETH when that validator is proven to have broken specific consensus rules. It exists to make certain kinds of misbehavior — primarily actions that could be used to attack finality itself, like signing two different blocks for the same slot — economically irrational rather than merely discouraged.

The behaviors that trigger slashing are narrow and specific: double voting, surround voting, and proposing two different blocks at the same height are the core examples. Ordinary downtime or a missed attestation is penalized separately, through smaller, non-slashing penalties, not through slashing itself.

Why it matters

Slashing is the mechanism that makes Ethereum’s finality guarantee credible: reverting a finalized block would require getting a large portion of the validator set to commit a slashable offense, which costs them real staked ETH. For anyone staking directly, running validator software correctly and keeping signing keys from running in two places at once is what keeps this risk near zero — it’s an operational hazard, not something that happens to well-run validators by chance.

Example

An operator misconfigures backup validator infrastructure so two machines sign attestations for the same validator key at the same time. The protocol detects the double signature and slashes a portion of that validator’s stake.

Not financial advice. This page explains how the mechanism works; it is not a recommendation to stake, restake, bridge, or trade anything.

Related · Staking

← All glossary terms

Not financial advice.