In plain English
What Slashing means
Proof-of-stake networks rely on validators to help confirm blocks and agree on the chain’s history. Slashing makes certain dishonest or conflicting behavior financially costly. It differs from ordinary missed-performance penalties: a validator that is briefly offline may lose modest rewards or incur a routine penalty, while slashing is reserved for defined misconduct that can threaten consensus.
Why it matters
Anyone operating a validator, delegating through a staking arrangement, or assessing a staking provider should understand slashing exposure. A validator can be slashed through deliberate misconduct, but operational errors can also create risk—for example, running the same validator key on two machines without proper signing-history protection. Network rules determine whether delegators share a loss.
Example
On Ethereum, a validator that signs two different blocks for the same slot can be slashed. Its staked ETH is subject to an immediate penalty, a forced exit process, and potentially a larger correlation penalty if many validators are slashed around the same time. The precise loss is protocol-dependent and can change; it is not a fixed percentage for every incident.
Quick answers
Common questions
Can a validator be slashed for being offline?+
Usually, ordinary downtime is handled through missed rewards or separate inactivity penalties rather than slashing. However, rules differ by protocol, and extended disruption can still cause meaningful losses or operational consequences.
Why is double signing dangerous?+
Signing conflicting blocks or attestations can help create incompatible versions of chain history. Slashing discourages that behavior by making a validator’s stake economically at risk when verifiable evidence of the violation is included.
Sources