Slashing is a protocol penalty that can remove part of a validator's staked coins after a provable violation of network rules. A validator briefly going offline is not slashed on every network, and some Proof of Stake networks do not use slashing at all. Who bears a loss also differs between solo staking, delegation, pools and exchanges, so check both the coin's rules and the provider's terms.
In crypto staking, validators put coins at stake as economic collateral. When a network can prove that a validator performed a prohibited action, the protocol may destroy part of that stake. This is slashing.
The aim is not to punish every technical problem severely. It is designed to discourage behaviour that can damage consensus or network security, such as signing contradictory messages. Offences and penalties differ by blockchain.
Slashing is also not a price loss. A slash reduces the number of coins in the staking position. A market price decline without a protocol penalty is a separate risk.
| Event | What happens? | Is it always slashing? |
|---|---|---|
| Missed reward | No payment for a duty not performed | No |
| Small protocol penalty | Balance falls because of absence or another network rule | Not every network calls this slashing |
| Slashing | A provable violation activates an explicit penalty against stake | Yes |
| Price decline | The market value of the coin falls | No |
| Provider loss | A company cannot return the coins | No; this is counterparty risk |
A lower balance does not automatically prove slashing. Use an official explorer or validator report to identify the recorded event.
On Ethereum, proposing two blocks for the same slot and signing contradictory attestations are well-known slashable offences. They produce cryptographic evidence for statements that cannot both be valid.
A common cause is running the same validator key on two active machines. Each instance can sign a different message. A poorly controlled failover server can therefore be more dangerous than a short period of downtime.
Other networks may penalise duplicate signing, invalid blocks or prolonged absence. Never use Ethereum’s rules as the universal definition for every coin.
An offline Ethereum validator misses rewards and can incur an inactivity penalty, but ordinary downtime is not itself slashing. In a long period without network finality, inactivity penalties can increase to help the network recover.
Other networks can place prolonged downtime under a specific penalty rule. Cosmos chains, for example, configure downtime and double-signing parameters per chain.
Ask not only whether slashing exists, but which uptime is required, how long recovery can take and what an ordinary absence costs.
Some protocols increase the penalty when many validators commit the same offence around the same time. The network treats an isolated error differently from an event affecting a large part of consensus.
This matters when validators share software, cloud infrastructure or a managed operator. A defect in one widely used setup can hit many positions together. Genuine diversification of clients, operators and infrastructure can reduce correlated risk.
Proof of Stake does not define one common penalty system.
| Network | Broad approach | What to check |
|---|---|---|
| Ethereum | Specific contradictory validator messages can be slashed | Key security, validator operation and client diversity |
| Cosmos chains | Rules may penalise downtime and double signing | Parameters of the particular chain |
| Polkadot | Misconduct can affect validators and nominators supporting them | Validator selection, incident scope and nomination terms |
| Cardano | Delegated ADA is not slashed by the protocol | Pool performance and missed rewards still matter |
| Solana | Current official guidance does not describe automatic protocol slashing as active | Current network rules and validator performance |
Network upgrades and governance can change these rules. Check current official documentation rather than relying solely on a general staking guide.
With solo staking, a protocol penalty directly affects your validator position. You are responsible for keys, software, monitoring and safe failover procedures.
On some networks, delegated coins can share a slashing loss. On others, only the validator is affected or delegators merely miss rewards. Check the coin’s rules rather than relying on the word delegation.
Do not choose a validator only by expected reward. Consider its history, commission, technical transparency and concentration. The exchange versus own wallet guide compares responsibilities.
A pool often spreads stake across validators. One validator incident may therefore affect only part of the assets. The pool may distribute a loss across token holders, use a reserve or apply another method under its terms.
With liquid staking, a slashing loss can appear in protocol value or in the relationship between the staking token and underlying coin. Check whether a reserve or insurance mechanism exists and which exclusions apply.
An exchange may absorb slashing, pass it to customers or include exceptions in its terms. Search the
product terms for slashing, validator penalties, losses and reward adjustments.
A MiCA licence does not provide general compensation for slashing. Custody regulation and staking risk are separate. See what MiCA protects.
Restaking can use an Ethereum staking position as collateral for additional services. The validator remains subject to Ethereum’s rules and can accept more duties elsewhere. That adds potential loss conditions.
For every service, identify the provable offence, who can initiate a penalty and how disputes or settlement work. An additional reward belongs to an additional obligation. Do not assume an LRT is exposed only to ordinary Ethereum slashing.
Ethereum has a standard interchange format for slashing protection data. It helps clients avoid signing a conflicting message after migration, but it is not a substitute for safe procedures.
The phrase slashing protection does not automatically promise compensation. Check whether it
describes a technical safeguard or a contractual cover.
There is no reliable percentage covering all staking products. Probability and potential loss depend on network rules, validator conduct, concentration, software and how a provider allocates losses.
Slashing may not be the largest financial risk. Price losses, account compromise, a smart contract exploit or provider insolvency can be more severe. Keep the technical penalty in proportion to the full risk profile. The article on crypto staking risks compares these risks across network staking, liquid staking and central providers.
We collect rates directly from providers through their APIs or official websites and check them daily. Every rate shows when it was last checked. Providers can change terms without notice, so confirm the current rate before depositing.
Crypto returns are never guaranteed. On-chain staking can involve slashing, liquid staking adds smart contract and depeg risk, and lending can expose your entire deposit if a provider fails. In every category, a fall in the coin price can exceed the rewards earned.
StakingRewards.eu compares and explains; it does not provide investment advice. Some links are affiliate links, which may earn us a fee. This does not affect the table order, which is based on the displayed rate.