Proof-of-Stake keeps validators honest with money at risk. The sharpest part of that risk is slashing — and it's worth understanding exactly what does and doesn't trigger it.
What slashing is
Slashing destroys a portion of a validator's staked deposit as punishment for provable misbehaviour. It's the protocol's way of making an attack on consensus expensive: cheat in a way the chain can prove, and you lose real value.
Slashing is what gives Proof-of-Stake its teeth. A miner who tries to cheat in Proof-of-Work merely wastes electricity; a validator who tries to cheat in Proof-of-Stake can have their own capital burned.
What gets a validator slashed
Slashing targets equivocation — saying two contradictory things the protocol can prove:
- Double proposing — producing two different blocks for the same slot.
- Contradictory attestations — casting attestation votes that conflict (for example, a "double vote" or a "surround vote") in a way that would help split the chain.
The common thread is that each is provable from on-chain evidence. The protocol doesn't need to judge intent; the contradictory messages themselves are the proof.
What is not slashing
A crucial distinction: being offline is not slashing. A validator that goes down and misses its duties suffers small inactivity penalties — a gentle leak that nudges validators to stay online. That's very different from the serious penalty of slashing.
| Behaviour | Consequence |
|---|---|
| Offline / missing duties | Small inactivity penalty |
| Double propose / contradictory attest | Slashing (part of stake burned) |
So a flaky internet connection won't get you slashed — only behaviour that looks like an attack on consensus will.
Why it's rare
In practice, slashing is uncommon. Honest validator software following the rules simply doesn't equivocate, and most slashings that do happen are accidents (for example, running the same validator keys on two machines at once, which can cause double signing). The takeaway for anyone watching the chain: a slashing event is notable precisely because it's unusual.
Seeing it on the explorer
Quantascan indexes slashing events on the penalties page. On a healthy network it's usually empty — which is exactly what you want to see.
Where to go next
- Validators and staking — what's at stake.
- Proof-of-Stake on QRL 2.0 — the security model.
- Slots, epochs and the beacon chain — where equivocation would happen.