Operator maintenanceSynthetic evidence · demo

Prysm 5.0.4 — signer migration

Incident · OP-MAINT-2026-04-26Window · Sun Apr 26, 2026 · 19:42 → 20:05 UTCDuration · 23 min

The operator intentionally stopped validator services to roll out Prysm 5.0.4 and migrate signing infrastructure. Missed duties occurred inside the signed maintenance window.

§ 01

Timeline

19:00 UTCOperator posts maintenance notice for Prysm rollout and signer migration.

19:42 UTCValidator services are stopped for controlled migration.

19:51 UTCMissed duties observed while signer keys are rotated.

20:05 UTCServices return after operator-controlled rollout completes.

20:30 UTCMaintenance window closed. No provider outage reported.

§ 02

Cause

Intentional operator action. The interruption is tied to scheduled maintenance, not AWS us-east-1 infrastructure failure.

§ 03

Impact

Validators affectedDemo operator cohort during maintenance

Slashing eventsSynthetic missed-duty slash in window

GeographyProvider and region match, but cause is excluded

§ 04

Machine-readable classification

{
  "kind": "OPERATOR_MAINTENANCE",
  "provider_attributed": false,
  "operator_attributed": true,
  "malicious": false,
  "excluded_under_policy": true
}

Note. This document is synthetic, written to demonstrate the kind of exclusion evidence SlashShield's GenLayer contract reasons over. No real operator or validator incident is referenced.