On September 10, a rare large-scale slashing event occurred on the Ethereum (ETH) beacon chain, with 40 validators penalized for submitting conflicting proofs, resulting in a total loss of over $52,000. On-chain data shows that the incident is related to multiple validation service providers, with Ankr-related nodes being the most severely affected.
Event Overview: 40 validators slashed
According to the beacon chain data, each affected validator was slashed about 0.3 ETH (approximately 1,300 USD), with total losses potentially exceeding 52,000 USD. Initial reports listed StakeFi, Allnodes, and SSV Network as related parties, but further investigation revealed that most nodes have direct connections with Ankr.
Cause of Incident: Double Signing Triggers Slashing
Ethereum core developer Preston Vanloon explained that slashing usually occurs when validators violate consensus rules and publish conflicting proofs. Such errors are common when a validator's key is running in multiple environments simultaneously, leading to inconsistent views of the chain among nodes, ultimately triggering double signing.
Vanloon speculates that this incident may be related to the operational errors of the validator service provider during the migration of validators.
Subsequent Impact: Must Continue to Operate After Slashing
The development team reminds that the slashed validators must continue to fulfill their duties until they formally exit the network. If they go offline during the exit queue, they will incur additional activity penalties.
Currently, slashing has already taken effect, and the upcoming penalties will be limited to loss of activity, but for the operators, the financial and reputational impacts can no longer be ignored.
Historical Background: Large-scale slashing events are rare but costly
Migalabs data shows that since the launch of the Ethereum beacon chain in 2020, only 525 validators have encountered slashing. This year, apart from this incident, only 15 similar cases have occurred.
However, historical cases indicate that once a slashing event escalates, the losses can be extremely severe—In November 2023, nearly 100 validators associated with Bitcoin Suisse were slashed for submitting incorrect proofs, resulting in losses close to $200,000.
Conclusion
The recent incident involving the slashing of 40 validators due to double signing once again highlights the economic discipline under Ethereum's PoS consensus mechanism - any operational mistake can directly translate into financial loss. For validator service providers and node operators, strict key management and migration process control are key to preventing similar incidents from recurring.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Ethereum slashing incident! 40 validators lost over $52,000 due to double signing.
On September 10, a rare large-scale slashing event occurred on the Ethereum (ETH) beacon chain, with 40 validators penalized for submitting conflicting proofs, resulting in a total loss of over $52,000. On-chain data shows that the incident is related to multiple validation service providers, with Ankr-related nodes being the most severely affected.
Event Overview: 40 validators slashed
According to the beacon chain data, each affected validator was slashed about 0.3 ETH (approximately 1,300 USD), with total losses potentially exceeding 52,000 USD. Initial reports listed StakeFi, Allnodes, and SSV Network as related parties, but further investigation revealed that most nodes have direct connections with Ankr.
Cause of Incident: Double Signing Triggers Slashing
Ethereum core developer Preston Vanloon explained that slashing usually occurs when validators violate consensus rules and publish conflicting proofs. Such errors are common when a validator's key is running in multiple environments simultaneously, leading to inconsistent views of the chain among nodes, ultimately triggering double signing.
Vanloon speculates that this incident may be related to the operational errors of the validator service provider during the migration of validators.
Subsequent Impact: Must Continue to Operate After Slashing
The development team reminds that the slashed validators must continue to fulfill their duties until they formally exit the network. If they go offline during the exit queue, they will incur additional activity penalties.
Currently, slashing has already taken effect, and the upcoming penalties will be limited to loss of activity, but for the operators, the financial and reputational impacts can no longer be ignored.
Historical Background: Large-scale slashing events are rare but costly
Migalabs data shows that since the launch of the Ethereum beacon chain in 2020, only 525 validators have encountered slashing. This year, apart from this incident, only 15 similar cases have occurred.
However, historical cases indicate that once a slashing event escalates, the losses can be extremely severe—In November 2023, nearly 100 validators associated with Bitcoin Suisse were slashed for submitting incorrect proofs, resulting in losses close to $200,000.
Conclusion
The recent incident involving the slashing of 40 validators due to double signing once again highlights the economic discipline under Ethereum's PoS consensus mechanism - any operational mistake can directly translate into financial loss. For validator service providers and node operators, strict key management and migration process control are key to preventing similar incidents from recurring.