The Ethereum ecosystem has seen only 226 validators slashed since the launch of the Beacon Chain on Dec. 1, 2020 \u2014 amounting to just 0.04% of 524,060 validators,\u00a0according to an Ethereum core developer.<\/p>\n
Slashing is a process where a validator breaches the proof-of-stake consensus rules, which often results in the removal of that validator from the network and slashing a portion of the staked Ether (ETH<\/a>)\u00a0that the validator provided as collateral. <\/p>\n Such slim odds of being slashed were\u00a0highlighted<\/a> by Ethereum core developer \u201cSuperphiz\u201d in a Feb. 23 Twitter post, which suggests that people shouldn\u2019t be concerned about staking ETH for that particular reason.<\/p>\n 226 out of 523,000 validators on the beacon chain have been slashed. This is nothing to lose sleep over. Many slashings have occurred during failed system migration. Here are four emerging best practice tips to avoid this:https:\/\/t.co\/wleR4YQmDD<\/a><\/p>\n \u2014 superphiz.eth (@superphiz) February 22, 2023<\/a><\/p><\/blockquote>\n The developer also explained \u201cfour emerging best practices\u201d to reduce those odds even further.<\/p>\n One of these practices was to wipe any existing chain data on old staking machines and to reinstall and reformat the validator where necessary, said Superphiz, noting that many slashings occur due to \u201cfailed systems migrations.\u201d<\/p>\n Superphiz then suggested using \u201cdoppelganger detection,\u201d which checks whether the validator\u2019s keys are active before starting the validation process.<\/p>\n While this can impact validator uptime, he explained that \u201cperfect uptime\u201d isn\u2019t worth getting slashed in the grand scheme of things:<\/p>\n \u201cIt’s wise to throw away $0.06 to save $1700. (A slashing costs about 1 Ether).\u201d<\/p><\/blockquote>\n The developer said it is also worth watching buffers and logs on the Beacon Chain to become aware of any potential problems that may arise. <\/p>\n If something feels wrong, Superphiz suggested \u201cunplugging everything\u201d and to \u201ccome back\u201d when the problem has been identified and a proposed solution is set in place. <\/p>\n The developer also noted that over 150 of the 226 slashings have been caused by services rather than \u201chome stakers.\u201d\u00a0<\/p>\n Slashing can occur due to an \u201cattestation\u201d or a \u201cproposal\u201d violation, according to the Ethereum Foundation.<\/p>\n An attestation violation is one where a malicious validator attempts to change the history of a block or \u201cdouble votes\u201d by attesting two candidates for the same block.<\/p>\n A proposal violation occurs when a validator proposes and signs two different blocks for the same slot.<\/p>\n The majority of slashing events have come from attestation violations, according<\/a> to data from beaconcha.in.<\/p>\n One of the largest slashing events occurred on Feb. 4, 2021, when staking infrastructure provider \u201cStaked\u201d had 75 of its validators slashed for producing competing blocks<\/a>.\u00a0Staked said the attestation violation came about due to a \u201ctechnical issue.\u201d<\/p>\n Related: <\/em><\/strong>What are the risks of the Ethereum Merge?<\/em><\/strong><\/a><\/p>\n Since the Beacon Chain merged with the Ethereum proof-of-work chain<\/a> on Sept. 15, only 35 of the total 226 slashings have taken place, according to beaconcha.in, which suggests that the Merge has not had a profound impact on slashing rates<\/a>.<\/p>\n With about 16.7 million ETH staked (according to beaconcha.in) out of 120.4 million ETH currently in circulation\u00a0 (according<\/a> to CoinGecko), the percentage of ETH staked is about 13.9%. <\/p>\n\n
![\"\"](\"https:\/\/s3.cointelegraph.com\/uploads\/2023-02\/213b79d3-6a53-41c5-be08-aee9fc638897.jpg\" "\\"\\"")
![\"\"](\"https:\/\/s3.cointelegraph.com\/uploads\/2023-02\/96681323-7170-426e-9f19-862158b0e6a9.jpg\" "\\"\\"")