Slashing is a penalty where a proof-of-stake network burns part of a validator's staked tokens for provable misbehavior — usually double-signing or surround-voting. It is not a gradual leak from downtime. It is a sudden, protocol-enforced burn that can also eject the validator from the active set. Whether you run a node or delegate to one, the loss can reach your own balance.
What actually triggers a slashing event
Most networks define a short list of slashable offenses, and they all involve equivocation — voting or signing against yourself. Honest mistakes like a power outage or a flaky connection don't slash you. They just cost you rewards.
Double-signing
Your validator signs two different blocks at the same height. This usually happens when someone runs the same validator key on two machines at once. A hurried migration to new hardware, with the old server still running, is the classic cause.
Surround voting
On networks like Ethereum, a validator can be slashed for casting votes that contradict its own earlier votes in a way the protocol can prove. It is rarer than double-signing but just as punishable.
How the penalty is calculated
There is no single global number. Each chain sets its own rules, and on Ethereum the size of the burn scales with how much total stake was slashed around the same time. A lone offender loses less than a coordinated attack would.
| Component | What it means |
|---|---|
| Initial penalty | A base burn applied immediately when the offense is proven |
| Correlation penalty | An extra burn that grows if many validators are slashed together |
| Ejection | The validator is removed from active duty and stops earning |
| Exit delay | Staked funds stay locked for a period before withdrawal |
That exit delay is the part people forget. Even after the burn, your capital is frozen while the network waits to be sure no further offenses surface.
A concrete scenario: the cost of one careless migration
Say you delegate to a validator with 1,000 tokens at stake, and that operator double-signs during a server move. On a network with a modest base penalty, you might lose a small percentage of your delegated amount, then sit locked out for days or weeks. If the slash is larger, the loss compounds because you are also missing rewards the whole time you are ejected.
Scale that up. A validator with 32 ETH self-staked plus delegated funds from dozens of users can see the operator's own bond wiped out first, and delegators share the remainder. One misconfigured backup node. Weeks of lost yield. That is the real bill.
How to reduce your exposure
If you delegate
- Check the validator's track record and whether it publishes its infrastructure setup.
- Spread stake across several operators rather than one.
- Confirm the network's slashing parameters before you commit, since they differ by chain.
- Ask operators how they handle failover, and watch for anyone running redundant keys carelessly.
If you run a node
- Never run the same validator key on two machines. Use a proper key-management or remote-signer setup.
- Test migrations on a separate key first.
- Keep signing keys offline where the design allows it.
- Monitor for missed attestations — they are an early warning something is wrong.
Platforms like MGBX publish validator and staking information that can help you compare operators before delegating, though you should still verify the underlying network rules yourself.
Frequently asked questions
Does downtime get you slashed?
No. Missing blocks or attestations only reduces your rewards, sometimes called a leak or inactivity penalty. Slashing is reserved for provable equivocation or protocol-defined offenses. A validator that simply goes offline loses income but keeps its principal intact.
Can I lose more than my original stake?
On most major networks the penalty is capped at the staked amount, so you cannot go negative. Check the specific chain's rules, because caps and correlation multipliers vary. Some newer designs handle this differently, so read the parameters before staking.
How long are funds locked after a slash?
It depends on the network, but many enforce an exit queue measured in days to weeks. During that window your tokens cannot be withdrawn and earn nothing. Plan around it if you might need liquidity.
Is slashing common?
On well-run networks it is relatively rare, because most operators follow key-management best practices. The events that do happen tend to cluster around migrations and infrastructure changes. That is exactly why operators with clear procedures are worth favoring.
Before you delegate a single token, pull up the validator's history and the network's slashing parameters side by side. Two minutes of checking beats a locked position you didn't see coming.