{"id":21465,"date":"2025-02-25T10:15:36","date_gmt":"2025-02-25T08:15:36","guid":{"rendered":"https:\/\/forklog.com\/en\/ethereums-pectra-update-on-holesky-testnet-faces-setbacks\/"},"modified":"2025-02-25T10:15:36","modified_gmt":"2025-02-25T08:15:36","slug":"ethereums-pectra-update-on-holesky-testnet-faces-setbacks","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/ethereums-pectra-update-on-holesky-testnet-faces-setbacks\/","title":{"rendered":"Ethereum&#8217;s Pectra Update on Holesky Testnet Faces Setbacks"},"content":{"rendered":"<p>On February 24th, at epoch 115,968, Ethereum developers activated the Pectra hard fork on the Holesky testnet. As a result, the network ceased finalizing slots.<\/p>\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"343\" src=\"https:\/\/forklog.com\/wp-content\/uploads\/Slots-Open-Source-Ethereum-ETH-Holesky-Testnet-Explorer-beaconcha.in-2025-Google-Chrome-1024x343.jpg\" alt=\"Slots-Open-Source-Ethereum-ETH-Holesky-Testnet-Explorer-beaconcha.in-2025-Google-Chrome\" class=\"wp-image-252629\" srcset=\"https:\/\/forklog.com\/wp-content\/uploads\/Slots-Open-Source-Ethereum-ETH-Holesky-Testnet-Explorer-beaconcha.in-2025-Google-Chrome-1024x343.jpg 1024w, https:\/\/forklog.com\/wp-content\/uploads\/Slots-Open-Source-Ethereum-ETH-Holesky-Testnet-Explorer-beaconcha.in-2025-Google-Chrome-300x101.jpg 300w, https:\/\/forklog.com\/wp-content\/uploads\/Slots-Open-Source-Ethereum-ETH-Holesky-Testnet-Explorer-beaconcha.in-2025-Google-Chrome-768x257.jpg 768w, https:\/\/forklog.com\/wp-content\/uploads\/Slots-Open-Source-Ethereum-ETH-Holesky-Testnet-Explorer-beaconcha.in-2025-Google-Chrome.jpg 1364w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\">Data: <a href=\"https:\/\/holesky.beaconcha.in\/\">beaconcha.in<\/a>.<\/figcaption><\/figure>\n<p>According to Parithosh Jayanthi from the Ethereum Foundation, the upgrade &#8220;encountered a configuration issue on three major network clients.&#8221; Fixes are already prepared, and operators need to update their software, he added.<\/p>\n<blockquote class=\"twitter-tweet\" data-conversation=\"none\" data-lang=\"en\">\n<p lang=\"en\" dir=\"ltr\">The Pectra fork adds a lot of new config values, these are usually system contracts . However, EIP-6110 moves the deposits detection from the domain of the CL to the domain of the EL. <\/p>\n<p>This implies the EL needs to configure the deposit contract.<br \/>(2\/13)<a href=\"https:\/\/t.co\/c5ev3RfnA1\">https:\/\/t.co\/c5ev3RfnA1<\/a><\/p>\n<p>\u2014 parithosh | ???? (@parithosh_j) <a href=\"https:\/\/twitter.com\/parithosh_j\/status\/1894236679411830937?ref_src=twsrc%5Etfw\">February 25, 2025<\/a><\/p><\/blockquote>\n<p> <script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script>\u00a0<\/p>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>&#8220;The Pectra hard fork adds many new configuration values, which are typically system contracts. However, <span data-descr=\"Ethereum Improvement Proposal \u2014 \u043f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u043f\u043e \u0443\u043b\u0443\u0447\u0448\u0435\u043d\u0438\u044e Ethereum\" class=\"old_tooltip\">EIP<\/span>-6110 moves deposit detection from the <span data-descr=\"\u0443\u0440\u043e\u0432\u0435\u043d\u044c \u043a\u043e\u043d\u0441\u0435\u043d\u0441\u0443\u0441\u0430\" class=\"old_tooltip\">CL<\/span> domain to the <span data-descr=\"\u0443\u0440\u043e\u0432\u0435\u043d\u044c \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f\" class=\"old_tooltip\">EL<\/span> domain. This means execution-level settings are required,&#8221; Jayanthi explained.<\/p>\n<\/blockquote>\n<p>The identified bug does not affect the main network and is related to Holesky&#8217;s peculiarities, the developer clarified.<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"en\">\n<p lang=\"en\" dir=\"ltr\">This might sound weird, but before Pectra EL clients didn\u2019t have to \u201cknow\u201d that the deposit contract was special because the CL just read from it directly. <\/p>\n<p>Now, because deposits can be triggered by the EL and aren\u2019t delayed by 2048 blocks (to account for PoW reorgs pre-merge),\u2026 <a href=\"https:\/\/t.co\/CVuf5r6thM\">https:\/\/t.co\/CVuf5r6thM<\/a><\/p>\n<p>\u2014 timbeiko.eth (@TimBeiko) <a href=\"https:\/\/twitter.com\/TimBeiko\/status\/1894177342295244981?ref_src=twsrc%5Etfw\">February 25, 2025<\/a><\/p><\/blockquote>\n<p> <script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>&#8220;The issue arose because Holesky (and Sepolia) deposit contracts are at a different address than the main network. Why? I have no idea,&#8221; confirmed Ethereum team lead Tim Beiko.<\/p>\n<\/blockquote>\n<p>The team will discuss further actions to resume the testnet&#8217;s operation during a teleconference.<\/p>\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>&#8220;The error will give us insight into how the mainnet would operate if such a scenario arises. This will provide us ample time to address issues before they become critical,&#8221; Jayanthi emphasized.<\/p>\n<\/blockquote>\n<p>The activation of the Pectra hard fork on the Sepolia test network is tentatively <a href=\"https:\/\/forklog.com\/en\/news\/ethereum-developers-consider-accelerating-network-upgrades\">scheduled<\/a> for March 5th.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On February 24th, at epoch 115,968, Ethereum developers activated the Pectra hard fork on the Holesky testnet. As a result, the network ceased finalizing slots. Data: beaconcha.in. According to Parithosh Jayanthi from the Ethereum Foundation, the upgrade &#8220;encountered a configuration issue on three major network clients.&#8221; Fixes are already prepared, and operators need to update [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":21464,"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-21465","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":"34","promo_type":"","layout_type":"","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/21465","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=21465"}],"version-history":[{"count":0,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/21465\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/21464"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=21465"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=21465"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=21465"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}