Slashing
A penalty in proof-of-stake networks where part of a validator’s stake is destroyed for misbehavior such as double-signing or extended downtime. A core security mechanism enforcing honest participation.
How slashing works
The mechanic:
- Validators stake tokens as collateral for honest participation.
- Specific misbehaviors are detected (signing conflicting blocks, extended downtime, attesting incorrectly).
- Penalty applied — portion of stake is destroyed.
- Severity varies by offense — minor downtime vs. major attacks.
The economic logic: misbehavior costs more than the gains from misbehaving.
Slashable offenses
Different chains define different offenses. Common ones:
- Double signing — proposing two blocks at the same height.
- Surround voting — attesting in conflicting ways.
- Extended downtime — not participating when expected.
- Specific protocol violations — implementation-specific.
Each offense has defined penalty.
How slashing affects validators
Practical effects:
- Direct loss of stake — fraction destroyed.
- Reduced rewards during downtime.
- Possible removal from validator set in severe cases.
- Reputation damage affecting delegations.
For validators, even modest slashing can be expensive on large stakes.
Slashing in practice
How often it happens:
- Most validators never get slashed with reasonable operational practices.
- Major slashing events are rare.
- Hardware/software failures sometimes cause minor slashing.
- Coordinated attacks would face massive slashing.
The deterrent effect keeps validators careful.
EigenLayer and restaking slashing
Restaking introduces additional slashing:
- Validators face standard chain-level slashing plus AVS-specific slashing.
- Multiple potential slashings stack on the same staked capital.
- AVS rules define specific slashing conditions.
- Cascading slashing risk — single event affecting multiple validators.
This is part of why restaking adds risk beyond standard staking.
What individuals should know
For users:
- Slashing affects delegators — choose validators carefully.
- Staking through pools typically distributes slashing risk.
- Liquid staking tokens absorb proportional slashing.
For validators:
- Operational reliability matters enormously.
- Backup infrastructure helps avoid downtime slashing.
- Best practices dramatically reduce slashing risk.
Slashing is the security mechanism that makes proof-of-stake economically secure. Its existence ensures attacking the network is much more expensive than it would otherwise be.