20 Ethereum Validators Slashed in Three Hours: Reasons


article image

Vladislav Sopov

Novel Ethereum (ETH) blockchain on proof of stake (PoS) witnessed its first massive slashing event

Contents

Seasoned Ethereum (ETH) developer, founding partner in Prysmatic Labs development studio Terence Tsao, unveiled the possible reasons of an unusual slasing event in proof-of-stake (PoS) Ethereum (ETH).

20 Ethereum (ETH) validators penalized in three hours

According to a tweet shared by Mr. Tsao, yesterday, Sept. 23, 2022, a total of 20 validators were slashed during three hours only.

Validators were penalized due to attester equivocation issues. As validator addresses and indices deposit data are not published, Mr. Tsao admitted the theat that the real causes of the issues are still shady.

However, it is highly likely that these slashing events were caused by duplicated setups and doppelganger detection failure.

Ads

As stated in Ethereum 2.0 documentation, Doppelganger Protection is a critical mechanism as:

Running the same validator twice will inevitably result in slashing

Who are Ethereum (ETH) validators and why is it necessary to slash some of them?

Mr. Tsao also stressed that the penalty for slashing and for being offline will be increased with every next upgrade Ethereum on PoS will undergo.

Ethereum (ETH) validators are responsible for the integrity of the Ethereum (ETH) blockchain consensus, correct block addition and transaction procession.

To prevent them from cheating and acting against the network, the Ethereum (ETH) design features strict penalties for validators’ misbehavior.

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *

Previous post Global Blockchain in Retail Market to Hit $3.27B by 2028
Next post Bitcoin’s assessment of the last 365 days reveals this about BTC’s future

Fatal error: Uncaught Error: Call to undefined function jnews_encode_url() in /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-content/plugins/jnews-social-share/class.jnews-select-share.php:225 Stack trace: #0 /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-content/plugins/jnews-social-share/class.jnews-select-share.php(357): JNews_Select_Share::get_select_share_data('facebook', false) #1 /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-content/plugins/jnews-social-share/class.jnews-select-share.php(65): JNews_Select_Share->build_social_button('facebook') #2 /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-includes/class-wp-hook.php(303): JNews_Select_Share->render_select_share('') #3 /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #4 /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #5 /homepages/36/d855603311/htdocs/clickandbuil in /homepages/36/d855603311/htdocs/clickandbuilds/ChainRadar/wp-content/plugins/jnews-social-share/class.jnews-select-share.php on line 225