Ethereum’s Beacon Chain recorded a major slashing event on Sept. 10, with 40 validators penalized for pushing conflicting attestations.Initial reports pointed to validator nodes tied to StakeFi, Allnodes, and SSV Network. However, further on-chain investigation showed that most affected operators were connected to Ankr.

Ethereum’s Beacon Chain recorded a major slashing event on Sept. 10, with 40 validators penalized for pushing conflicting attestations.Initial reports pointed to validator nodes tied to StakeFi, Allnodes, and SSV Network. However, further on-chain investigation showed that most affected operators were connected to Ankr.
Cryptoslate
Revision history

5 recorded changes

Want your article here?

Promote with Leviathan News

Ethereum’s Beacon Chain experienced one of its largest proof‑of‑stake slashing events on September 10, when around 39–40 validators were penalized for conflicting attestations (double-signing) in a correlated time window. Beaconcha.in data cited in reports shows that at least one validator lost about 0.3 ETH in the process; extrapolated across the entire group, total losses are estimated at over $50,000 at then-prevailing prices. Under Ethereum’s slashing rules, such behavior is treated as potentially attack‑like, so slashed validators are forcibly exited and face both an immediate balance cut and additional correlated penalties when many are slashed in a short period. Initial community analysis tentatively linked the affected validators to infrastructure and staking providers including StakeFi, Allnodes, and SSV Network, but subsequent on‑chain investigation indicated that most of the impacted validator operators were associated with Ankr, a major staking and infrastructure provider. Ethereum core developer Preston Van Loon attributed the root cause to validator keys being run on multiple systems or environments, likely during migrations or maintenance, causing nodes to see divergent chain views and submit conflicting attestations that automatically trigger slashing under consensus rules. Reporting around the incident stresses that this was an operational error by staking operators rather than a protocol bug or malicious attack, yet it underscores how misconfigured validator setups—especially with distributed validator technology and third‑party operators—can still lead to sizable, irreversible losses even in a mature proof‑of‑stake environment.

AI-generated background, compiled from web sources — not editorial content.

More coverage

Explore the topic

More on Ethereum

Comments