{"id":17580,"date":"2026-02-23T16:58:49","date_gmt":"2026-02-23T16:58:49","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/02\/23\/pectra-testnet-announcement-ethereum-foundation-blog\/"},"modified":"2026-02-23T16:58:49","modified_gmt":"2026-02-23T16:58:49","slug":"pectra-testnet-announcement-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/02\/23\/pectra-testnet-announcement-ethereum-foundation-blog\/","title":{"rendered":"Pectra Testnet Announcement | Ethereum Foundation Blog"},"content":{"rendered":"<p> <br \/>\n<br \/><img decoding=\"async\" src=\"https:\/\/storage.googleapis.com\/ethereum-hackmd\/upload_c953ed34b3d2227e1ec03710bbb229b4.jpg\" \/><\/p>\n<div id=\"\">\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"05032025-sepolia-incident-update\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"05032025 sepolia incident update permalink\" href=\"#05032025-sepolia-incident-update\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>[05\/03\/2025] Sepolia Incident Update<\/h2>\n<p class=\"chakra-text css-gi02ar\">See <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2025\/03\/05\/sepolia-pectra-incident\">this post<\/a>.<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"27022025-holesky-incident-update\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"27022025 holesky incident update permalink\" href=\"#27022025-holesky-incident-update\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>[27\/02\/2025] Holesky Incident Update<\/h2>\n<p class=\"chakra-text css-gi02ar\">On Feb. 24, 2025, the Pectra upgrade activated on the Holesky testnet. After the activation, a configuration issue in Besu, Nethermind and go-ethereum led to a chain split on Holesky. The issue was rapidly fixed, but the Holesky network performance is still degraded. More details on the incident can be found <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md\">here<\/a>.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"sepolia-network-upgrade\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"sepolia network upgrade permalink\" href=\"#sepolia-network-upgrade\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Sepolia Network Upgrade<\/h3>\n<p class=\"chakra-text css-gi02ar\">The Sepolia network upgrade timing is <strong>unchanged<\/strong>. The network is expected to fork at epoch <span class=\"chakra-text css-ons8vw\">222464<\/span> (Mar. 5, 7:29 UTC). Node operators using the <strong>Besu<\/strong>, <strong>go-ethereum<\/strong>, <strong>Nethermind<\/strong> or <strong>Lodestar<\/strong> clients <strong>MUST<\/strong> upgrade their client prior to the upgrade. The latest releases can be found in the table below.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"holesky-coordinated-slashing\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"holesky coordinated slashing permalink\" href=\"#holesky-coordinated-slashing\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Holesky Coordinated Slashing<\/h3>\n<p class=\"chakra-text css-gi02ar\">If you run a Holesky validator, please follow these instructions <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md#holesky-coordinated-slashings\">in this document<\/a> to help the network stabilize.<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"pectra-overview\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"pectra overview permalink\" href=\"#pectra-overview\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Pectra Overview<\/h2>\n<p class=\"chakra-text css-gi02ar\">It will go live on Holesky at epoch <span class=\"chakra-text css-ons8vw\">115968<\/span> (Feb. 24, 21:55 UTC) and then on Sepolia at epoch <span class=\"chakra-text css-ons8vw\">222464<\/span> (Mar. 5, 7:29 UTC). The Pectra testnet client releases are listed <a class=\"chakra-link css-vezwxf\" href=\"http:\/\/blog.ethereum.org\/2025\/02\/14\/pectra-testnet-announcement#client-releases\">below<\/a>. Once both testnets have successfully upgraded, a mainnet activation epoch will be chosen.<\/p>\n<p class=\"chakra-text css-gi02ar\">Pectra follows last year&#8217;s <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2024\/02\/27\/dencun-mainnet-announcement\">Dencun upgrade<\/a>. It introduces features to augment Ethereum accounts, improve the validator experience, support L2 scaling, and more!<\/p>\n<p class=\"chakra-text css-gi02ar\">This post explores these three major improvements in detail. For a more comprehensive overview, see <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/ethereum.org\/en\/roadmap\/pectra\/\">ethereum.org&#8217;s guide to the upgrade<\/a>.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"from-eoas-to-smart-accounts\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"from eoas to smart accounts permalink\" href=\"#from-eoas-to-smart-accounts\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>From EOAs to Smart Accounts<\/h3>\n<p class=\"chakra-text css-gi02ar\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7702\">EIP-7702<\/a> represents a major step toward widespread account abstraction, enabling users to enhance their Externally Owned Accounts (<a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/ethereum.org\/en\/developers\/docs\/accounts\/\">EOAs<\/a>) with smart contract functionality.<\/p>\n<p class=\"chakra-text css-gi02ar\">This hybrid approach combines the simplicity of EOAs with the programmability of contract-based accounts. In practice, it enables:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><strong>Transaction batching<\/strong>, where multiple operations execute atomically within a single transaction. No more separate transactions for &#8220;approve&#8221; and &#8220;swap&#8221;!<\/li>\n<li class=\"css-0\"><strong>Gas sponsorship<\/strong>, which allows others to pay for transaction fees. This is especially useful when wanting to transact from an account that doesn&#8217;t have ETH in it.<\/li>\n<li class=\"css-0\"><strong>Alternative authentication<\/strong>, which means many <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/en.wikipedia.org\/wiki\/Hardware_security_module\">hardware security modules<\/a> (HSMs) in phones today can be used to authorize operations for the account via technologies like <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/fidoalliance.org\/passkeys\/\">passkeys<\/a>.<\/li>\n<li class=\"css-0\"><strong>Spending controls<\/strong>, which can limit how many tokens a specific application can spend, or cap daily outflows from a wallet, improving security.<\/li>\n<li class=\"css-0\"><strong>Recovery mechanisms<\/strong>, which provide different options for users to safeguard their assets, without migrating to a new account.<\/li>\n<\/ul>\n<p class=\"chakra-text css-gi02ar\">To use EIP-7702, an EOA signs an authorization pointing to a specific delegation address whose code it wants to execute. Once set, the account gains the new code\u2019s capabilities (e.g., batching, sponsorship, authentication logic, etc.). Because choosing a delegation target hands over a great deal of control, EIP-7702 enforces several safety checks:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\"><strong>Chain-specific delegations<\/strong>: by default, a delegation is only valid on a specific chain ID, preventing the same authorization from being used on different networks.<\/li>\n<li class=\"css-0\"><strong>Nonce-bound delegations<\/strong>: authorizations can be tied to the account&#8217;s current nonce, automatically invalidating them once the nonce increases.<\/li>\n<li class=\"css-0\"><strong>Revocability<\/strong>: the owner of the EOA can always create another EIP-7702 authorization that revokes or replaces the existing delegation code, preventing a permanent lock-in if something goes wrong.<\/li>\n<\/ul>\n<p class=\"chakra-text css-gi02ar\">For a deeper dive into how this all works, see <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.youtube.com\/watch?v=_k5fKlKBWV4\">@lightclient&#8217;s Devcon talk on the topic<\/a>.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"validator-ux-improvements\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"validator ux improvements permalink\" href=\"#validator-ux-improvements\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Validator UX Improvements<\/h3>\n<p class=\"chakra-text css-gi02ar\">Three new EIPs within Pectra improve the validator experience: <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7251\">7251<\/a>, <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7002\">7002<\/a> and <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-6110\">6110<\/a>.<\/p>\n<p class=\"chakra-text css-gi02ar\">The first, EIP-7251, raises the maximum balance a validator can receive rewards on from 32 ETH to 2048 ETH, through an opt-in update of withdrawal credential type.<\/p>\n<p class=\"chakra-text css-gi02ar\">For smaller stakers, this enables automatic reward compounding. Previously, any rewards earned beyond a validator&#8217;s 32 ETH deposit would not count towards their active stake. Stakers who wanted to stake more than 32 ETH could only do so in fixed 32 ETH increments, relying on staking pools for anything in between. With EIP-7251, both existing and new validators can be configured to earn rewards on the entirety of their stake, up to 2048 ETH per validator.<\/p>\n<p class=\"chakra-text css-gi02ar\">This EIP also allows larger operators to consolidate multiple validators. To do so, they must first designate a target validator on which to enable compounding, and then initiate a consolidation request from another source validator. To understand the mechanics in detail, watch this talk from <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.youtube.com\/watch?v=EwW6dNi9VCY\">Teku&#8217;s Paul Harris<\/a>.<\/p>\n<p class=\"chakra-text css-gi02ar\">EIP-7002 also extends validators&#8217; abilities, this time by introducing execution layer triggerable withdrawals. Prior to this EIP, only a validator&#8217;s active signing key could trigger an exit. Now, if an Ethereum address is set as a withdrawal credential, that too can force an exit. This reduces trust assumptions in delegation settings, as the owner of the funds &#8212; be they a human in control of an EOA or a DAO-managed smart contract &#8212; can always trustlessly initiate an exit.<\/p>\n<p class=\"chakra-text css-gi02ar\">Lastly, EIP-6110 removes a lingering vestige of pre-merge Ethereum: the delay between validator deposits and their addition to the deposit queue. Pre-merge, the Beacon Chain had to wait 2048 blocks before processing validator deposits to account for potential proof-of-work re-orgs. This is no longer necessary!<\/p>\n<p class=\"chakra-text css-gi02ar\">With EIP-6110, deposit processing delays now drop from around 9 hours to roughly 13 minutes. Teku engineers Lucas Saldanha and Stefan Bratanov covered the details of EIP-7002 and EIP-6110 in their <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.youtube.com\/watch?v=EyDChjFQEkQ\">joint Devcon SEA talk<\/a>.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"blob-scaling-oo\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"blob scaling oo permalink\" href=\"#blob-scaling-oo\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Blob Scaling .oO<\/h3>\n<p class=\"chakra-text css-gi02ar\">The final major change in Pectra is EIP-7691, increasing Ethereum\u2019s blob capacity by 50%!<\/p>\n<p class=\"chakra-text css-gi02ar\">Blobs, introduced in the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7569\">Dencun upgrade<\/a>, are ephemeral data storage that L2s can use to submit compressed transaction data and proofs to Ethereum L1. Since going live, they&#8217;ve reduced L1 fees for L2s by 10-100x, resulting in far cheaper L2 user transactions.<\/p>\n<p class=\"chakra-text css-gi02ar\">The Ethereum mainnet currently supports an average of 3 blobs per block, with a maximum of 6 to accommodate periods of high demand. With EIP-7691, these numbers will increase to an average of 6 and maximum of 9.<\/p>\n<p class=\"chakra-text css-gi02ar\">Unlike <span class=\"chakra-text css-ons8vw\">CALLDATA<\/span>, which nodes store indefinitely, blobs are pruned from the network after 4096 epochs (~18 days). This bounds the amount of disk space they can use. The binding constraint for blobs is instead bandwidth, as blobs need to be gossiped over Ethereum&#8217;s peer-to-peer layer. To offset the bandwidth increase caused by EIP-7691, Pectra also introduces EIP-7623, which caps the worst-case size of a block.<\/p>\n<p class=\"chakra-text css-gi02ar\">To continue scaling Ethereum\u2019s data throughput without a corresponding rise in bandwidth requirements, we must shift from a world where every node stores every blob to one where nodes store only a subset and sample the network to verify the remaining blob data. Good news: work to support this is already underway! Francesco from the Ethereum Foundation research team outlined this scaling roadmap in his <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.youtube.com\/watch?v=toR2UKzE_zA\">devcon keynote<\/a>.<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"pectra-specifications\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"pectra specifications permalink\" href=\"#pectra-specifications\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Pectra Specifications<\/h2>\n<p class=\"chakra-text css-gi02ar\">The list of changes introduced in Pectra can be found in <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7600\">EIP-7600<\/a>. For reference, they are:<\/p>\n<p class=\"chakra-text css-gi02ar\">Additionally, full python specification for the changes to the execution and consensus layer specifications can be found in the following releases:<\/p>\n<p class=\"chakra-text css-gi02ar\">Lastly, Pectra also introduces changes to the Engine API used for communication between the consensus and execution layer nodes. These are specified in the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/execution-apis\/blob\/main\/src\/engine\/prague.md\"><span class=\"chakra-text css-ons8vw\">prague.md<\/span><\/a> file of the repository.<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"pectra-activation\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"pectra activation permalink\" href=\"#pectra-activation\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Pectra Activation<\/h2>\n<p class=\"chakra-text css-gi02ar\">The Pectra network upgrade will activate on Holesky and Sepolia as follows:<\/p>\n<p class=\"chakra-text css-gi02ar\">Additionally, Pectra has already been activated on Ephemery, a staking testnet which resets every 28 days. Read more about it <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ephemery-testnet\/ephemery-resources?tab=readme-ov-file#pectra\">here<\/a>.<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"client-releases\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"client releases permalink\" href=\"#client-releases\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Client Releases<\/h2>\n<p class=\"chakra-text css-gi02ar\"><strong>Important note:<\/strong> during to the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md\">Holesky incident<\/a>, issues were found with the <strong>Besu<\/strong>, <strong>go-ethereum<\/strong>, <strong>Nethermind<\/strong> and <strong>Lodestar<\/strong> clients. The tables below have been updated with new releases for each of these clients. Node operators <strong>MUST<\/strong> upgrade to the latest versions before the Sepolia network ugprade activation to address the issue triggered on Holesky.<\/p>\n<p class=\"chakra-text css-gi02ar\">The following client releases are suitable for the Pectra upgrade on <strong>both<\/strong> Holesky and Sepolia. Further versions will activate support on mainnet. Once these are released, another announcement will be made on this blog.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"consensus-layer-sepolia--holesky-releases\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"consensus layer sepolia  holesky releases permalink\" href=\"#consensus-layer-sepolia--holesky-releases\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Consensus Layer Sepolia &amp; Holesky Releases<\/h3>\n<p class=\"chakra-text css-gi02ar\"><em class=\"chakra-text css-0\">When running a validator, both the Consensus Layer Beacon Node and Validator Client must be updated.<\/em><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>[27\/02] Notes<\/strong>:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">The Lodestar version was updated from 1.27.0 to 1.27.1 following the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md\">Holesky incident<\/a>.<\/li>\n<li class=\"css-0\">The Grandine client was <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/grandinetech\/grandine\/releases\/tag\/0.4.0\">open-sourced in April 2024<\/a>. Since then, it has been included in all Pectra testing efforts alongside other clients.<\/li>\n<\/ul>\n<h4 class=\"chakra-heading group css-qm6a1\" id=\"execution-layer-sepolia--holesky-releases\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"execution layer sepolia  holesky releases permalink\" href=\"#execution-layer-sepolia--holesky-releases\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Execution Layer Sepolia &amp; Holesky Releases<\/h4>\n<hr aria-orientation=\"horizontal\" class=\"chakra-divider css-1e6gg7n\"\/>\n<p class=\"chakra-text css-gi02ar\"><strong>Notes:<\/strong><\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">[05\/03] All versions above were updated to address the <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2025\/03\/05\/sepolia-pectra-incident\">Sepolia incident<\/a>.<\/li>\n<li class=\"css-0\">[04\/03] The Reth version was updated from 1.2.0 to 1.2.1 to fix a Sepolia configuration issue.<\/li>\n<li class=\"css-0\">[27\/02] The Besu version was updated from 25.2.0 to 25.2.1 following the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md\">Holesky incident<\/a>.<\/li>\n<li class=\"css-0\">[27\/02] The go-ethereum version was updated from 1.15.1 to 1.15.3 following the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md\">Holesky incident<\/a>.<\/li>\n<li class=\"css-0\">[27\/02] The Nethermind version was updated from 1.31.0 to 1.31.2 following the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/blob\/master\/Pectra\/holesky-postmortem.md\">Holesky incident<\/a>.<\/li>\n<\/ul>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"faq\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"faq permalink\" href=\"#faq\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>FAQ<\/h2>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"how-do-ethereum-network-upgrades-work\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"how do ethereum network upgrades work permalink\" href=\"#how-do-ethereum-network-upgrades-work\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>How do Ethereum network upgrades work?<\/h3>\n<p class=\"chakra-text css-gi02ar\">Ethereum network upgrades require explicit opt-in from node operators on the network. While client developers come to consensus on what EIPs are included in an upgrade, they are not the ultimate deciders of its adoption.<\/p>\n<p class=\"chakra-text css-gi02ar\">For the upgrade to go live, validators and non-staking nodes must manually update their software to support the protocol changes being introduced.<\/p>\n<p class=\"chakra-text css-gi02ar\">If they use an Ethereum client that is not updated to the latest version (listed above), at the fork block, it will disconnect from upgraded peers, leading to a fork on the network. In this scenario, each subset of the network nodes will only stay connected with those who share their (un)upgraded status.<\/p>\n<p class=\"chakra-text css-gi02ar\">While most Ethereum upgrades are non-contentious and cases leading to forks have been rare, the option for node operators to coordinate on whether to support an upgrade or not is a key feature of Ethereum&#8217;s governance.<\/p>\n<p class=\"chakra-text css-gi02ar\">For a more exhaustive overview of Ethereum&#8217;s governance process, see <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.youtube.com\/watch?v=HoclxIBR2EM\">this talk by Tim Beiko<\/a>.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-an-ethereum-mainnet-user-or-eth-holder-is-there-anything-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as an ethereum mainnet user or eth holder is there anything i need to do permalink\" href=\"#as-an-ethereum-mainnet-user-or-eth-holder-is-there-anything-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As an Ethereum mainnet user or $ETH holder, is there anything I need to do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">In short, no.<\/p>\n<p class=\"chakra-text css-gi02ar\">This announcement only pertains to Ethereum testnets: Holesky and Sepolia. A further announcement will be made for Pectra&#8217;s activation on the Ethereum mainnet, but even then, Ethereum mainnet users and $ETH holders are not expected to have to take action.<\/p>\n<p class=\"chakra-text css-gi02ar\">If you&#8217;d like to watch the upgrade go live on Holesky, EthStaker is hosting an <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/www.youtube.com\/live\/XfdDV0RhDyI\">online viewing party<\/a>!<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-non-staking-sepolia-or-holesky-node-operator-what-do-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a non staking sepolia or holesky node operator what do i need to do permalink\" href=\"#as-a-non-staking-sepolia-or-holesky-node-operator-what-do-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a non-staking <strong>Sepolia or Holesky<\/strong> node operator, what do I need to do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">To be compatible with the upgrade on either testnet, update your node&#8217;s execution and consensus layer clients to the versions listed in the table above.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-sepolia-or-holesky-staker-what-do-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a sepolia or holesky staker what do i need to do permalink\" href=\"#as-a-sepolia-or-holesky-staker-what-do-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a <strong>Sepolia or Holesky<\/strong> staker, what do I need to do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">To be compatible with the upgrade on either testnet, update your node&#8217;s execution and consensus layer clients to the versions listed in the table above. <strong>Make sure both your beacon node and validator client are updated.<\/strong><\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-non-sepolia-or-holesky-node-operator-or-staker-what-do-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a non sepolia or holesky node operator or staker what do i need to do permalink\" href=\"#as-a-non-sepolia-or-holesky-node-operator-or-staker-what-do-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a non-Sepolia or Holesky node operator or staker, what do I need to do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">Nothing for now. Further announcements will be made for Pectra&#8217;s activation on mainnet.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-an-application-or-tooling-developer-what-should-i-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as an application or tooling developer what should i do permalink\" href=\"#as-an-application-or-tooling-developer-what-should-i-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As an application or tooling developer, what should I do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">Review the EIPs included in Pectra to determine if and how they affect your project &#8212; there are many new exciting features being introduced across both the execution and consensus layers!<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-security-researcher-what-should-i-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a security researcher what should i do permalink\" href=\"#as-a-security-researcher-what-should-i-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a security researcher, what should I do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">Keep an eye out for a post about the Pectra bug bounty competition <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/x.com\/cantinaxyz\/status\/1889660786936885365\">coming soon<\/a> \ud83d\udc40<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"why-pectra\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"why pectra permalink\" href=\"#why-pectra\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Why &#8220;Pectra&#8221;?<\/h3>\n<p class=\"chakra-text css-gi02ar\">Upgrades to the execution layer follow Devcon city names, and those to the consensus layer use star names. &#8220;Pectra&#8221; is the combination of Prague, the location of Devcon IV, and Electra, a blue-white giant star in the constellation of Taurus.<\/p>\n<hr aria-orientation=\"horizontal\" class=\"chakra-divider css-1e6gg7n\"\/>\n<p class=\"chakra-text css-gi02ar\">Original cover image by <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/unsplash.com\/photos\/red-and-white-concrete-houses-at-daytime--WNG-ErziqM\">Julia Solonina<\/a>, with modifications by <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/twitter.com\/tomosaito\">Tomo Saito<\/a>.<\/p>\n<\/div>\n<p><script async src=\"\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><br \/>\n<br \/><br \/>\n<br \/><a href=\"https:\/\/blog.ethereum.org\/en\/2025\/02\/14\/pectra-testnet-announcement\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[05\/03\/2025] Sepolia Incident Update See this post. [27\/02\/2025] Holesky Incident Update On Feb. 24, 2025, the Pectra upgrade activated on the Holesky testnet. After the activation, a configuration issue in Besu, Nethermind and go-ethereum led to a chain split on Holesky. The issue was rapidly fixed, but the Holesky network performance is still degraded. More [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":17532,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-17580","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17580","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=17580"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17580\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/17532"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=17580"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=17580"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=17580"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=17580"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}