{
  "id": 8045,
  "title": "EIP-8045: Exclude slashed validators from proposing",
  "status": "Draft",
  "type": "Standards Track",
  "category": "Core",
  "summary": "After a slashing event, punished validators can still be scheduled to propose blocks, causing missed slots and slow recovery. This change simply skips slashed validators so healthy ones keep proposing and the chain keeps running.",
  "impacts": [
    "Users should experience fewer stalled slots and better network responsiveness after large validator slashings, because only non-slashed validators will propose blocks.",
    "Application behavior during recovery from mass slashings becomes more predictable, with fewer missed blocks and smoother chain progress. No application changes required.",
    "Wallets get more consistent head updates after slashings, reducing confusing gaps in block production. No direct wallet code changes are expected.",
    "Indexers, explorers, and relays see steadier block flow after slashings, easing incident handling. No protocol-facing changes required for these services.",
    "L2 sequencers relying on L1 data and finality benefit from steadier L1 block production after slashings, improving uptime. No L2 code impact.",
    "Once slashed, a validator immediately loses proposer eligibility. Node operators must account for skipped proposing duties but otherwise run unchanged software.",
    "Consensus clients must update proposer selection logic to prefilter slashed validators using beacon state, integrate with EIP-7917 lookahead, and add tests.",
    "Execution clients are unaffected because block proposer selection lives in the consensus layer; no modifications are required in execution code.",
    "Maintains block production after mass slashing events.",
    "Improves chain resilience and recovery during network disruptions.",
    "Prevents wasting proposer slots on already slashed validators.",
    "Reduces prolonged degraded performance while slashed validators exit."
  ],
  "discussion_url": "https://ethereum-magicians.org/t/eip-8045-exclude-slashed-validators-from-proposing/25850",
  "source_markdown_url": "https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8045.md",
  "canonical_url": "/latest/eips/8045.json",
  "markdown_url": "/latest/eips/8045.md",
  "citations": [
    {
      "recordId": "eip-8045",
      "artifactPath": "normalized/8045.json",
      "url": "/records/proposal/eip-8045/normalized/8045.json",
      "label": "EIP-8045: Exclude slashed validators from proposing",
      "snippet": "After a slashing event, punished validators can still be scheduled to propose blocks, causing missed slots and slow recovery. This change simply skips slashed validators so healthy ones keep proposing and the chain keeps"
    }
  ]
}