What Is Slashing?
Slashing is a penalty mechanism in proof-of-stake blockchains that punishes validators for provably malicious or negligent behavior by destroying a portion of their staked tokens. The threat of slashing is what keeps validators honest — the economic cost of misbehaving must far exceed any potential gain from an attack. Slashing protects network security by ensuring that validators have a strong financial incentive to follow protocol rules at all times.
Table of Contents
What Is Slashing?
Slashing is the enforced destruction of a validator's staked tokens as punishment for protocol violations. It is the most severe penalty in proof-of-stake systems and is reserved for actions that could compromise network security. The slashed tokens are typically burned (permanently destroyed) rather than redistributed, ensuring that no one profits from the penalty. The severity of slashing depends on the offense and how many validators are involved.
Slashable Offenses
The two primary slashable offenses across most PoS chains are double-signing (proposing two different blocks for the same slot) and surround voting (making contradictory attestations that could enable chain reorganizations). On Ethereum, both offenses trigger an initial penalty plus a correlation penalty that scales with the number of validators slashed in the same timeframe. Extended downtime is not slashable on Ethereum but results in accumulated attestation penalties.
Impact on Stakers and Delegators
When a validator is slashed on Ethereum, they lose at least 1/32 of their stake initially, followed by a correlation penalty calculated over the following 36 days. In the worst case (one-third of all validators slashed), the entire stake can be destroyed. On Cosmos chains, slashing for double-signing typically results in 5% stake destruction, while downtime slashing takes 0.01%. Delegators on affected validators share in these losses proportionally.
Preventing Slashing
The most important prevention measure is never running two instances of the same validator simultaneously, as this can cause double-signing. Use slashing protection databases that track previous signing history. Keep validator software updated to avoid bugs that could produce conflicting messages. Use remote signer setups with hardware security modules for additional protection. As a delegator, choose validators with established track records, diverse client software, and professional operating practices.
Frequently Asked Questions
Has slashing actually happened on Ethereum?
Yes, though it is rare. Most Ethereum slashing events have been caused by technical misconfiguration rather than malicious intent, such as running duplicate validator instances or using outdated software. The penalties for isolated slashing events are relatively small (1 ETH initially), but correlated slashing (many validators slashed simultaneously) triggers much larger penalties.
Can delegators be slashed?
On some networks, yes. On Cosmos chains, delegator stakes can be partially slashed if their validator misbehaves. On Ethereum, slashing affects the validator's 32 ETH stake directly. Liquid staking protocols may socialize slashing losses across all stakers. This is why choosing reliable validators and diversifying delegation is important.