The post Ethereum Beacon Chain sees major slashing event with 40 validators penalized appeared on BitcoinEthereumNews.com. 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. Beacon Chain reported that one validator was “slashed’ 0.3 ETH, which was worth roughly $1,300 at the time. If similar losses occurred across the group, the cumulative penalty could exceed $52,000. What went wrong? Slashing occurs when validators act against consensus rules, often by publishing contradictory attestations. Preston Vanloon, an Ethereum core developer, explained that such errors usually appear when validator keys are run across multiple environments. In that situation, nodes may see different views of the chain, leading to double-signing and automatic penalties. He said: “These validators published conflicting attestations.” Vanloon further agreed that the issue might have stemmed from the impacted firms’ committing a blunder while migrating a validator. 3 Seconds Now. Gains That Compound for Years. Act fast to join the 5-day Crypto Investor Blueprint and avoid the mistakes most investors make. Brought to you by CryptoSlate Nice 😎 Your first lesson is on the way. Please add [email protected] to your email whitelist. Meanwhile, the Ethereum developer stressed that the validators must keep operating until they exit the network despite the fines. According to him: “Slashed validators are obligated to continue performing their duties until they are exited. If they are offline during the exit queue, then they will have liveness penalties applied. The slashing penalty has already been applied so it’s just the liveness penalties from here.” Ethereum slashing Mass slashing remains a rare occurrence on Ethereum, as evidenced by the fact that, apart from the recent one, there have only been 15 such cases this year. Migalabs’ data shows that… The post Ethereum Beacon Chain sees major slashing event with 40 validators penalized appeared on BitcoinEthereumNews.com. 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. Beacon Chain reported that one validator was “slashed’ 0.3 ETH, which was worth roughly $1,300 at the time. If similar losses occurred across the group, the cumulative penalty could exceed $52,000. What went wrong? Slashing occurs when validators act against consensus rules, often by publishing contradictory attestations. Preston Vanloon, an Ethereum core developer, explained that such errors usually appear when validator keys are run across multiple environments. In that situation, nodes may see different views of the chain, leading to double-signing and automatic penalties. He said: “These validators published conflicting attestations.” Vanloon further agreed that the issue might have stemmed from the impacted firms’ committing a blunder while migrating a validator. 3 Seconds Now. Gains That Compound for Years. Act fast to join the 5-day Crypto Investor Blueprint and avoid the mistakes most investors make. Brought to you by CryptoSlate Nice 😎 Your first lesson is on the way. Please add [email protected] to your email whitelist. Meanwhile, the Ethereum developer stressed that the validators must keep operating until they exit the network despite the fines. According to him: “Slashed validators are obligated to continue performing their duties until they are exited. If they are offline during the exit queue, then they will have liveness penalties applied. The slashing penalty has already been applied so it’s just the liveness penalties from here.” Ethereum slashing Mass slashing remains a rare occurrence on Ethereum, as evidenced by the fact that, apart from the recent one, there have only been 15 such cases this year. Migalabs’ data shows that…