{"id":21931,"date":"2025-03-11T13:33:28","date_gmt":"2025-03-11T11:33:28","guid":{"rendered":"https:\/\/forklog.com\/en\/ethereum-testnet-holesky-resumes-after-pectra-update-glitch\/"},"modified":"2025-03-11T13:33:28","modified_gmt":"2025-03-11T11:33:28","slug":"ethereum-testnet-holesky-resumes-after-pectra-update-glitch","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/ethereum-testnet-holesky-resumes-after-pectra-update-glitch\/","title":{"rendered":"Ethereum Testnet Holesky Resumes After Pectra Update Glitch"},"content":{"rendered":"

At epoch 119,090, the Holesky test network restored its final state following a slot finalization glitch during the Pectra hard fork activation.<\/p>\n

\"1122145321\"
Data: X<\/a>.<\/figcaption><\/figure>\n

On February 24, developers implemented the update in the testnet. However, the upgrade encountered<\/a> a “configuration issue on three main network clients.” <\/p>\n

The identified bug was specific to Holesky and did not affect the main blockchain or Pectra.<\/p>\n

Parithosh Jayanthi from the Ethereum Foundation highlighted the role of developers Raphael Matias, Barnabas Busa, Sam Calder-Mason in restoring the testnet’s state, and particularly noted the “tools” from the specialist known as pk910.<\/p>\n

Activation<\/a> of Pectra on March 5 in another test network \u2014 Sepolia \u2014 also led to a failure<\/a>. In this instance, the cause was incorrect event generation by the deposit contract.<\/p>\n

After corrections were made, a malicious actor intervened<\/a>. They executed the previous scenario by sending a zero transaction. Developers admitted they overlooked this edge case.<\/p>\n

The team planned<\/a> to deploy Pectra on the Ethereum mainnet in early April.<\/p>\n","protected":false},"excerpt":{"rendered":"

At epoch 119,090, the Holesky test network restored its final state following a slot finalization glitch during the Pectra hard fork activation. Data: X. On February 24, developers implemented the update in the testnet. However, the upgrade encountered a “configuration issue on three main network clients.” The identified bug was specific to Holesky and did […]<\/p>\n","protected":false},"author":1,"featured_media":21930,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"","news_style_id":"","cryptorium_level":"","_short_excerpt_text":"","creation_source":"","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[46,268,1617,1134],"class_list":["post-21931","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-ethereum","tag-hardfork","tag-pectra","tag-technical-updates"],"aioseo_notices":[],"amp_enabled":true,"views":"24","promo_type":"","layout_type":"","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/21931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=21931"}],"version-history":[{"count":0,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/21931\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/21930"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=21931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=21931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=21931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}