Encyclopedia Ethereum · Entry 258
What happens when an Ethereum validator goes offline?
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Missed duties | Offline validators cannot perform their assigned duties. | [2] |
| Different offense | Being offline alone is not the same as signing conflicting messages. | [1] |
| Network condition | An inactivity leak changes penalties during extended non-finality. | [1] |
Find which part of the setup stopped working
The signing client depends on working consensus and execution infrastructure, synchronization and connectivity. An apparently running process can still be unable to perform useful duties if its node is behind or disconnected.
Check client health, synchronization and duty records before making changes. The operational question is whether valid, timely messages reached the network, not only whether the computer had power.
A short home outage is not a double vote
Suppose a validator misses several duties during a home connection outage. Those omissions can cost rewards and incur applicable inactivity penalties. They do not by themselves constitute two conflicting signed votes.
Starting a backup signer while the original may still be signing creates a different risk. Follow the client’s controlled failover process and preserve signing history.
The same duration can have different consequences
When the chain continues finalizing, ordinary missed-duty penalties apply. When finality stalls long enough, the inactivity-leak mechanism increases pressure on validators failing the relevant participation requirements.
Do not turn a single past outage bill into a universal hourly penalty quote. Effective balance, duty assignment, protocol version and network condition all matter.
Direct answers
Questions people ask
Will a power cut automatically slash my validator?
No. Downtime alone is not slashable. Specific conflicting proposals or attestations are different offenses, although missed duties still have costs.
Can I guarantee an exact loss for one offline hour?
Not from duration alone. The validator’s duties, balance and the network’s finality condition affect rewards and penalties.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
An offline Ethereum validator misses duties and rewards and may receive ordinary penalties. Downtime by itself is not a slashable offense. Slashing concerns specific conflicting signatures. The cost of being offline also depends on whether the network is finalizing normally; extended non-finality activates additional inactivity penalties. Diagnose the outage without hastily starting a second independent signer for the same key.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimMissed duties: Offline validators cannot perform their assigned duties.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimDifferent offense: Being offline alone is not the same as signing conflicting messages.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimNetwork condition: An inactivity leak changes penalties during extended non-finality.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Proof-of-stake rewards and penaltiesethereum.org contributors
Reward components, missed duties and penalty distinctions; values are not quoted as live rates.
Locator: Rewards; penalties; inactivity leak; slashing · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.371ZOpen source - Home staking Ethereumethereum.org contributors
Running and maintaining execution, consensus and validator infrastructure with a qualifying stake.
Locator: How it works; responsibilities; requirements · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.708ZOpen source - Slashing protection interchange formatEthereum Improvement Proposals
Signing-history transfer between validator clients does not authorize concurrent independent copies.
Locator: Interchange format; import and export; safety · Version / scope: EIP-3076 · Retrieved: 2026-10-02T18:55:26.323ZOpen source - Ethereum nodes and clientsethereum.org contributors
Post-Merge client roles, optional validators and synchronization modes.
Locator: Execution and consensus clients; synchronization; node types · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.405ZOpen 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. “What happens when an Ethereum validator goes offline?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-validator-downtime/