What is slashing in crypto? Staking penalties explained

Slashing is the penalty a proof of stake blockchain applies when a validator breaks its most important rules, such as signing two conflicting blocks. Part of the validator’s staked coins is destroyed and the validator is usually forced out of the network, so cheating costs real money.

If you stake crypto, through an exchange or on your own, slashing is one of the risks behind your rewards. For most ordinary stakers it is a small one, but it helps to know how it works and who pays when it happens.

What is slashing in crypto?

Slashing is the protocol’s way of punishing validator misconduct with financial penalties taken straight from the stake. In proof of stake protocols, validators lock up coins as collateral to earn the right to propose new blocks and vote on other validators’ blocks. If a validator breaks the consensus rules in a way that could harm the network, the protocol takes part of that collateral away.

That is the core of the slashing mechanism: honest validators earn staking rewards, misbehaving validators lose money. Because the punishment is automatic and written into the code, nobody has to trust a company or a court to enforce it.

Why proof of stake networks need slashing

PoS networks need slashing because staking alone doesn’t stop malicious behaviour. Without a penalty, a validator could vote for two competing versions of the chain at no cost, hoping one of them wins.

In a proof of work system like Bitcoin, attacking the network costs electricity and hardware. In proof of stake, the cost comes from the risk of losing staked assets. Slashing gives the consensus mechanism its economic incentives: network participants who attack the chain, for example by effectively changing history, lose part of their stake. This is what people mean by economic finality: once enough validators have voted for a block, reversing it would cost attackers a huge amount of slashed coins. It is a key part of network security and network integrity.

How slashing works

Slashing works by proving, on chain, that a validator signed two messages that can’t both be true. Any network participant who spots such a pair can submit it as evidence, and the protocol then penalises the slashed validator automatically.

What triggers slashing on Ethereum

On the Ethereum network, there are three slashable offences. All three are safety violations, not mistakes like being offline:

• Double signing blocks. A block proposer creates two different blocks for the same slot. This is a dishonest proposal, because it offers the network two versions of the same block.
• Double voting. A validator signs two different attestations (votes) for the same target epoch.
• Surround voting. A validator signs an attestation that “surrounds” an earlier one, which could help rewrite blocks that were already agreed on.

In each case the same validator signs two messages that conflict, using the same validator key. Two blocks for the same slot or conflicting attestations are what trigger slashing. Being offline (liveness faults) doesn’t: an offline Ethereum validator just misses rewards and pays small inactivity penalties.

What a slashing penalty looks like

Slashing penalties on Ethereum come in layers:

1. Initial penalty. A small fraction of the validator’s effective balance (the stake the protocol counts) is burned straight away.
2. Forced exit. The validator is removed from the validator set. It can’t earn rewards and waits about five weeks before the remaining stake can be withdrawn.
3. Correlation penalty. Midway through that period an additional penalty is applied, based on how many other validators were slashed around the same time. One isolated slashed validator loses little; if many validators are slashed at once in a coordinated attack, the penalty can rise to the entire stake.

That correlation penalty is the clever part. An honest mistake by one operator is cheap. An attack involving multiple validators is ruinous.

Slashing rules on other networks

Slashing rules differ between PoS networks. Many Cosmos-based chains slash for double signing and also for long downtime, with percentages set by each chain’s governance, and they temporarily “jail” the validator. On networks such as Polkadot and Cosmos, people who delegate to a validator can lose part of their delegated stake when it is slashed. Some networks, Cardano for example, don’t slash at all and rely on other incentives. Always check the rules of the specific network before you stake.

An example: what slashing means for your stake

Say you stake €2,000 of ETH through a staking provider, and one of the provider’s node operators runs the same validator on two servers for backup. Both copies sign a block for the same slot, and the validator is slashed. In an isolated case like this the initial loss is small, but the validator is forced to exit, so that part of the pool earns nothing for several weeks.

Whether you notice depends on the provider. If your €2,000 is spread across many validators, the hit is diluted. If the provider covers slashing losses, you may not lose anything. If its terms pass losses on to you, your balance drops. The bigger risk is a provider whose validators are all slashed together, for example after a software bug, because that is exactly the situation the correlation penalty punishes.

Slashing risk under MiCA

Staking is often not covered by MiCA, so in the EU you can’t assume a regulator has checked how slashing losses are handled. Licensed exchanges may offer staking as a separate product under separate terms. Bitvavo, for example, states that its staking and lending products are not regulated under MiCA (see our Bitvavo review), and Crypto.com says the same about its Earn and staking products (see our Crypto.com review).

In practice that means three checks before you stake on a platform:

• Who runs the validators: the exchange itself or a third party?
• Who pays if a validator is slashed: the provider or you?
• How long does it take to unstake, and what happens to your coins if the provider fails?

Our page on staking and our list of the best platforms for staking cover these points in more depth.

How validators avoid slashing

Node operators avoid slashing mainly by making sure the same validator key never runs in two places at once. Most real slashing events so far came from setups meant to improve performance or uptime, such as a backup machine that started signing while the main one was still running.

Good practice includes:

• Slashing protection. Validator client software keeps a slashing protection database that refuses to sign a message conflicting with an earlier one. Never delete it when moving a validator.
• One key, one machine. Accept a few minutes of downtime rather than running a validator twice.
• Client diversity. Using less common client implementations reduces the chance that a single bug affects most of the validator set at once.
• Careful migrations. Wait until the old machine has fully stopped before starting the new one.

If you don’t run a validator yourself, your main tool is choosing a provider with a clear track record on validator operations and clear terms on who bears slashing losses.

The bottom line

Slashing is what makes proof of stake costly to attack: validators that sign conflicting messages lose part of their stake and are forced out. For ordinary stakers it is a real but usually small risk, smaller than price swings or provider failure. Before you stake, check which network’s slashing rules apply and who pays if it happens.

Related terms

• Staking
• Validator
• Proof of stake
• Consensus mechanism
• Node