Slashing
Slashing destroys or confiscates stake and can force validator exit when provable behavior violates a proof-of-stake network's severe-fault rules.
Category: StakingStacked bars category cue
System record
Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.
Why it exists
Slashing makes certain conflicting or invalid validator actions economically costly enough to protect consensus safety and deter coordinated attacks.
Traditional-finance analogy
Forfeiture of a performance bond is the closest comparison recorded for this concept.
Where the analogy stops
- Protocol evidence and deterministic state transitions can impose loss without a court or discretionary claims process.
- Slashable conduct, penalty amount, correlation effects, whistleblower rewards, exit, and downstream delegation losses vary by network and service.
Main actors
- ActorSlashed validator operator
- ActorStake owner or delegator
- ActorEvidence submitter or whistleblower
- ActorOther validators and consensus protocol
- ActorStaking pool or liquid-staking holder
- ActorAdditional service with separate slashing authority
Assets and claims
Assets — controlled or transformed resources
Assets are resources the mechanism moves, holds, values, or transforms.
- AssetBonded stake
- AssetSlashing reward where applicable
Claims — entitlements and corresponding dependencies
Claims are rights to value, repayment, redemption, control, or another party's performance; each depends on an obligation or system that must honor it.
- ClaimReduced validator and delegator balance
- ClaimForced-exit and withdrawal claim
Slashing destroys or confiscates stake and can force validator exit after protocol-defined evidence proves a severe consensus fault.
Why it exists
Section titled “Why it exists”Some validator actions threaten consensus safety rather than only availability. Slashing makes conflicting or invalid signed messages costly and gives the network a deterministic way to remove the responsible validator under its fault and evidence assumptions.
Traditional-finance analogy
Section titled “Traditional-finance analogy”Forfeiture of a performance bond is a useful analogy. On-chain slashing can be triggered by protocol evidence without a court or discretionary claims process. Each network or additional service defines its own offense, proof, penalty, reward, exit, timing, and dispute model.
Penalty is not always slashing
Section titled “Penalty is not always slashing”A missed reward, ordinary downtime penalty, inactivity leak, forced exit, and slash are distinct state transitions. Calling every negative adjustment “slashing” hides the evidence threshold, severity, intent assumptions, and downstream loss.
Actors, assets, and claims
Section titled “Actors, assets, and claims”The validator operator controls the signing process; the stake owner or delegator bears economic exposure. Other validators and the protocol verify fault evidence. An evidence submitter can receive a network-defined reward. Pools, liquid-staking holders, and restakers may absorb downstream reductions even though they did not sign the offending message.
Step-by-step mechanism
Section titled “Step-by-step mechanism”- Define the exact slashable message conflict or service fault and its domain.
- Observe and submit complete evidence tied to a validator and protocol state.
- Verify signatures, chain, domain, timing, message relation, and prior processing.
- Mark the validator slashed and apply the immediate protocol-defined balance change.
- Process any delayed, correlation, inactivity, or additional-service component.
- Force or schedule exit and update the residual withdrawal claim.
- Allocate burn, evidence reward, pool loss, and downstream claim-token change.
State transition and propagation
Section titled “State transition and propagation”| Item | Before valid evidence | Slashing change | After |
|---|---|---|---|
| Validator status | Active or exiting | Marked slashed; forced process begins | Exited under network timing |
| Bonded stake | Supports validator duties | Penalty, burn, confiscation, or reward | Reduced residual withdrawal |
| Delegator or pool claim | Reflects share of controlled stake | Loss allocated by ownership/accounting | Lower claim value or balance |
| Downstream collateral | Valued from a staking claim | Price and solvency assumptions change | May face liquidation or bad debt elsewhere |
Capital flow moves destroyed stake and any evidence reward. Information flow is the signed messages, evidence, validator state, fault window, and correlation data. Claim flow reduces the stake owner’s withdrawal entitlement and any pooled or tokenized claim backed by that stake. Return flow can pay an evidence reward from issuance or penalized stake where the network defines one. Control flow includes evidence submission and protocol or service slashing authority. Risk flow can propagate from one validator into pooled claims, lending collateral, vaults, bridges, and restaked services.
Return source and loss allocation
Section titled “Return source and loss allocation”An evidence or whistleblower reward, where present, is funded from protocol issuance or the penalized stake under network rules. The slashed stake owner is the direct loss bearer; pool and claim holders bear it when contracts socialize or pass through validator loss. Insurance pays only within its explicit coverage and capacity.
Engineer or auditor lens
Section titled “Engineer or auditor lens”Test evidence authenticity, domain separation, validator identity, exact fault relation, replay, duplicate inclusion, cumulative penalties, correlation windows, integer bounds, exit ordering, withdrawals, whistleblower attribution, reorgs, base-chain versus service scope, and paused or upgraded states. Slashing protection must survive backup restore, failover, migration, and concurrent signers.
Ethereum’s rewards and penalties documentation describes one network’s slashable proposal and attestation conflicts, forced exit, and correlation effects. These offenses and penalty formulas are not universal. The documentation was reviewed 2026-08-10.
Common misunderstandings
Section titled “Common misunderstandings”- “Going offline once is slashing.” Many networks treat ordinary missed duties separately from severe slashable evidence.
- “Only the operator loses.” Stake owners, delegators, pooled claim holders, and downstream borrowers can bear the economic loss.
- “Slashing proves malicious intent.” A valid conflicting signature can result from key duplication, failover, or client faults even when intent is disputed.
Next follow pooled loss into liquid staking and added service conditions into restaking.
Machine-readable model
Key equations
Canonical expressions come from the structured concept record. KaTeX renders the notation, while the plain-text expression and variable table keep its meaning and units inspectable without JavaScript. Read the narrative above for the model's domain, assumptions, and rounding rules.
This concept does not require one canonical equation. Its mechanism and state transitions remain the authoritative explanation; do not invent a formula merely to make the topic look quantitative.
Assurance contract
Security properties
These structured statements define desired behavior. Their stable IDs can bind tests, invariants, specifications, audit findings, or proof results without turning descriptive review advice into an assurance claim.
Desired · not evaluated: No test, audit, or proof result is implied until scoped evidence is linked to this property.
Only protocol-defined evidence for the exact validator, chain, domain, and fault can trigger a slash
The same offense cannot be charged twice beyond the protocol's explicit cumulative-penalty model
Penalty, reward, burn, exit, and residual withdrawal amounts reconcile without creating or hiding stake
Base-chain and additional-service slashing scopes, authorities, delays, appeals, and maximum exposures remain explicit
Knowledge check
Quiz
Answer in your own words, then open the model answer.
What problem does Slashing exist to address?
Model answer
Slashing makes certain conflicting or invalid validator actions economically costly enough to protect consensus safety and deter coordinated attacks.