Encyclopedia Ethereum · Entry 17
Ethereum slashing: conflicting signatures, penalties and downtime
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Slashable behavior | Specific conflicting proposals or attestations | [1] |
| Ordinary absence | Missed rewards and penalties are distinct from slashing | [1] |
| Correlation | Losses can increase when many validators are slashed together | [1] |
The protocol evaluates signed messages, not a person’s intention
Slashable conditions concern contradictions in what a validator signs. Examples include proposing two different blocks for one slot, double-voting at the same target epoch or making a vote that surrounds another in the forbidden pattern.
The protocol can evaluate the messages without knowing why they were produced. Malice is one possibility, but operational mistakes can also create conflicting signatures.
Example: a backup must not become a second active signer
Imagine two machines both actively using the same validator key. If they follow different views of a slot and sign incompatible proposals or attestations, the resulting evidence can satisfy a slashing condition.
This is why redundancy is not simply copying keys and turning everything on. The relevant operational objective is continuity without contradictory signing; ordinary website-style failover assumptions do not establish that property.
Initial loss and correlated loss are different parts of the result
A slashing event forces an exit and applies penalties. The eventual amount depends on applicable protocol parameters and on other slashings around the event, rather than a universal fixed percentage quoted without context.
Correlated penalties make widespread conflicting behavior more costly. Older documentation can contain numeric examples from earlier upgrades; this entry deliberately avoids presenting those amounts as today’s calculator.
Being offline is harmful without automatically being slashable
A validator that misses normal duties can lose rewards and incur ordinary penalties. That is not identical to producing evidence of conflicting votes. Describing every connection outage as slashing blurs an important distinction.
During prolonged nonfinality, inactivity-leak penalties can become significant. The statement that routine absence is not itself a slashable offense is therefore not a promise that extended absence is cheap.
Direct answers
Questions people ask
Will a short internet outage automatically slash a validator?
Missing duties is not itself the same as the specific conflicting-signature conditions for slashing, although missed rewards and other penalties can apply.
Can a validator be slashed accidentally?
Yes. Operational errors such as conflicting signing with the same key can produce slashable evidence regardless of intent.
Is the loss always a fixed amount?
No. Protocol parameters, validator balance and correlated slashings affect the result. Historical examples should not be reused as a current universal amount.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Slashing penalizes specific conflicting validator actions, including double proposals, double votes and surround votes. It is different from ordinary missed-duty penalties. A slashed validator is forced to exit and can lose stake, with losses affected by correlated slashing. Accidental duplicated signing setups can produce slashable messages.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimSlashable behavior: Specific conflicting proposals or attestations
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimOrdinary absence: Missed rewards and penalties are distinct from slashing
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimCorrelation: Losses can increase when many validators are slashed together
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Proof-of-stake rewards and penaltiesethereum.org contributors
Supports ordinary nonparticipation penalties versus slashable conflicting proposals/votes. Inconsistent numeric examples are not reused.
Locator: Penalties; slashing; inactivity leak · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.680530+00:00Open source - Gasperethereum.org contributors
Supports fork choice versus checkpoint finality and the at-least-one-third conflicting-vote overlap argument.
Locator: What is finality; fork choice; inactivity leak · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.699844+00:00Open source - Solo stakingethereum.org contributors
Supports running execution/consensus/validator software and the operational nature of staking.
Locator: How it works; responsibilities; considerations · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.704988+00:00Open source - EIP-7251: Increase the MAX_EFFECTIVE_BALANCEEthereum Improvement Proposals
Defines 32 ETH minimum activation, 2,048 ETH maximum effective balance for compounding validators and changed withdrawal/penalty mechanics.
Locator: Constants; consensus layer; rationale · Version / scope: ac912ca6a9685590345dd8e5736cda75976d0131 · Retrieved: 2026-10-02T14:35:51.253355+00:00Open source - Proof of stakeethereum.org contributors
Supports 12-second slots, 32-slot epochs, stake-weighted checkpoint voting and block verification.
Locator: Validators; transaction execution; finality; fork choice · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.818781+00:00Open source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Ethereum slashing: conflicting signatures, penalties and downtime.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-slashing/