{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "ethereum-validator-downtime",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/ethereum-validator-downtime/",
  "collection": "ethereum",
  "title": "What happens when an Ethereum validator goes offline?",
  "description": "Understand missed validator duties, ordinary inactivity penalties and the difference between an outage and a slashable signature.",
  "aliases": [
    "Ethereum validator offline",
    "staking downtime penalties"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "ethereum-validator-downtime-quick-answer",
    "sourceIds": [
      "x425-eth-eth-rewards",
      "x425-eth-eth-solo",
      "x425-eth-eip3076"
    ]
  },
  "keyFacts": [
    {
      "label": "Missed duties",
      "value": "Offline validators cannot perform their assigned duties.",
      "sourceIds": [
        "x425-eth-eth-solo"
      ],
      "id": "missed-duties",
      "claimId": "ethereum-validator-downtime-fact-missed-duties"
    },
    {
      "label": "Different offense",
      "value": "Being offline alone is not the same as signing conflicting messages.",
      "sourceIds": [
        "x425-eth-eth-rewards"
      ],
      "id": "different-offense",
      "claimId": "ethereum-validator-downtime-fact-different-offense"
    },
    {
      "label": "Network condition",
      "value": "An inactivity leak changes penalties during extended non-finality.",
      "sourceIds": [
        "x425-eth-eth-rewards"
      ],
      "id": "network-condition",
      "claimId": "ethereum-validator-downtime-fact-network-condition"
    }
  ],
  "prerequisites": [
    "ethereum-slashing",
    "ethereum-proof-of-stake-finality"
  ],
  "sections": [
    {
      "id": "diagnosis",
      "heading": "Find which part of the setup stopped working",
      "sourceIds": [
        "x425-eth-eth-solo",
        "x425-eth-eth-nodes"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "example",
      "heading": "A short home outage is not a double vote",
      "sourceIds": [
        "x425-eth-eth-rewards",
        "x425-eth-eip3076"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "network",
      "heading": "The same duration can have different consequences",
      "sourceIds": [
        "x425-eth-eth-rewards"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Will a power cut automatically slash my validator?",
      "answer": "No. Downtime alone is not slashable. Specific conflicting proposals or attestations are different offenses, although missed duties still have costs.",
      "sourceIds": [
        "x425-eth-eth-rewards"
      ]
    },
    {
      "question": "Can I guarantee an exact loss for one offline hour?",
      "answer": "Not from duration alone. The validator’s duties, balance and the network’s finality condition affect rewards and penalties.",
      "sourceIds": [
        "x425-eth-eth-rewards"
      ]
    }
  ],
  "claims": [
    {
      "id": "ethereum-validator-downtime-quick-answer",
      "articleSlug": "ethereum-validator-downtime",
      "statement": "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.",
      "sourceIds": [
        "source-5c75a0594463b144",
        "source-ed235bbe5523f774",
        "source-9d546a950a3e1f5d"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-5c75a0594463b144",
          "locator": "Rewards; penalties; inactivity leak; slashing"
        },
        {
          "sourceId": "source-ed235bbe5523f774",
          "locator": "How it works; responsibilities; requirements"
        },
        {
          "sourceId": "source-9d546a950a3e1f5d",
          "locator": "Interchange format; import and export; safety"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read ordinary missed source/target vote penalties, missing proposer reward, slashing offences and inactivity leak. Draft correctly avoids treating an outage itself as slashable. Duplicate failover risk follows conflicting signatures and EIP3076; no unsupported estimate for a given number of offline hours."
        ]
      }
    },
    {
      "id": "ethereum-validator-downtime-fact-missed-duties",
      "articleSlug": "ethereum-validator-downtime",
      "statement": "Missed duties: Offline validators cannot perform their assigned duties.",
      "sourceIds": [
        "source-ed235bbe5523f774"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-ed235bbe5523f774",
          "locator": "How it works; responsibilities; requirements"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read ordinary missed source/target vote penalties, missing proposer reward, slashing offences and inactivity leak. Draft correctly avoids treating an outage itself as slashable. Duplicate failover risk follows conflicting signatures and EIP3076; no unsupported estimate for a given number of offline hours."
        ]
      }
    },
    {
      "id": "ethereum-validator-downtime-fact-different-offense",
      "articleSlug": "ethereum-validator-downtime",
      "statement": "Different offense: Being offline alone is not the same as signing conflicting messages.",
      "sourceIds": [
        "source-5c75a0594463b144"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-5c75a0594463b144",
          "locator": "Rewards; penalties; inactivity leak; slashing"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read ordinary missed source/target vote penalties, missing proposer reward, slashing offences and inactivity leak. Draft correctly avoids treating an outage itself as slashable. Duplicate failover risk follows conflicting signatures and EIP3076; no unsupported estimate for a given number of offline hours."
        ]
      }
    },
    {
      "id": "ethereum-validator-downtime-fact-network-condition",
      "articleSlug": "ethereum-validator-downtime",
      "statement": "Network condition: An inactivity leak changes penalties during extended non-finality.",
      "sourceIds": [
        "source-5c75a0594463b144"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-5c75a0594463b144",
          "locator": "Rewards; penalties; inactivity leak; slashing"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read ordinary missed source/target vote penalties, missing proposer reward, slashing offences and inactivity leak. Draft correctly avoids treating an outage itself as slashable. Duplicate failover risk follows conflicting signatures and EIP3076; no unsupported estimate for a given number of offline hours."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-eth-rewards",
      "label": "Proof-of-stake rewards and penalties",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/",
      "locator": "Rewards; penalties; inactivity leak; slashing",
      "note": "Reward components, missed duties and penalty distinctions; values are not quoted as live rates.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.371Z",
      "contentSha256": "a1279005274988597f18c77dd4dab93e5ab61e3835be5a0b9302c0bea85a5ff9",
      "recordId": "source-5c75a0594463b144"
    },
    {
      "id": "x425-eth-eth-solo",
      "label": "Home staking Ethereum",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/staking/solo/",
      "locator": "How it works; responsibilities; requirements",
      "note": "Running and maintaining execution, consensus and validator infrastructure with a qualifying stake.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:25.708Z",
      "contentSha256": "8892580b4f6bb823ebe817c3073ad9d7eb2c8b32b54e4645f8ff6d4cbc919d51",
      "recordId": "source-ed235bbe5523f774"
    },
    {
      "id": "x425-eth-eip3076",
      "label": "Slashing protection interchange format",
      "publisher": "Ethereum Improvement Proposals",
      "url": "https://eips.ethereum.org/EIPS/eip-3076",
      "locator": "Interchange format; import and export; safety",
      "note": "Signing-history transfer between validator clients does not authorize concurrent independent copies.",
      "version": "EIP-3076",
      "checkedAt": "2026-10-02T18:55:26.323Z",
      "contentSha256": "bf236c87eea59de6a6eb5fdfb802dffa5399004902cacc4f44522f4f80e95866",
      "recordId": "source-9d546a950a3e1f5d"
    },
    {
      "id": "x425-eth-eth-nodes",
      "label": "Ethereum nodes and clients",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/developers/docs/nodes-and-clients/",
      "locator": "Execution and consensus clients; synchronization; node types",
      "note": "Post-Merge client roles, optional validators and synchronization modes.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.405Z",
      "contentSha256": "504af7a98b297efac4a639ad20b92921c64db4df44e543acc2f75683f56420d2",
      "recordId": "source-81c7c6821c46702f"
    }
  ],
  "related": {
    "articles": [
      "ethereum-slashing",
      "ethereum-proof-of-stake-finality",
      "ethereum-nodes-rpc",
      "ethereum-validator-keys",
      "ethereum-client-diversity"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "Degrees 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/"
}