SSV Team Analyzes Recent Penalty Incidents Affecting Validators

According to BlockBeats, the SSV team has released a detailed analysis of two recent penalty incidents. The monitoring system first flagged a penalty event on Wednesday at 11:51 UTC. Approximately 90 minutes later, a larger penalty incident impacted 39 validators. Investigations revealed that both incidents were caused by external factors related to the SSV protocol, specifically concerning validator key management. The larger incident involved the long-term staking service provider Ankr, which admitted that a maintenance configuration error led to validator keys being active on two different infrastructures simultaneously, resulting in the penalty. Ankr promptly shut down the affected operators and collaborated with SSV Labs to identify the root cause. The smaller incident involved validators who had previously migrated from the custodial service provider Allnodes. This incident is still under investigation, but investigators suspect that auxiliary validator settings may have played a role. SSV Labs CEO Alon Muroch stated that the penalty incidents did not compromise the SSV protocol, and operators or stakeholders do not need to take any action. A review of the logs from both incidents showed no signs of double signing or faults on the SSV side.