{"id":18125,"date":"2026-03-09T22:40:04","date_gmt":"2026-03-09T22:40:04","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/09\/finalized-no-27-ethereum-foundation-blog\/"},"modified":"2026-03-09T22:40:04","modified_gmt":"2026-03-09T22:40:04","slug":"finalized-no-27-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/09\/finalized-no-27-ethereum-foundation-blog\/","title":{"rendered":"Finalized no. 27 | Ethereum Foundation Blog"},"content":{"rendered":"


\n
<\/p>\n

\n

tl;dr<\/p>\n

<\/g><\/svg><\/a>Upgrade for London, yes you!<\/h2>\n

The hotly anticipated upgrade to Ethereum mainnet — London — has a fork block scheduled, and mainnet client releases are out. As mentioned before, to allow for validator deposits, the beacon chain validators come to consensus on the state of the proof-of-work chain and process deposits sequentially from there.<\/p>\n

To maintain this link, all mainnet validators<\/em> must upgrade their proof-of-work nodes (often called the “eth1 endpoint”).<\/p>\n

Please see the London announcement<\/a> for more details.<\/p>\n

<\/g><\/svg><\/a>\ud83d\udea8\ud83d\udea8\ud83d\udea8 Warning \ud83d\udea8\ud83d\udea8\ud83d\udea8<\/em><\/h3>\n

Due to an issue uncovered last week on the Ropsten testnet (see restrospective<\/a>), Go-Ethereum (geth)<\/strong>, Nethermind<\/strong>, and Erigon<\/strong> have cut new, critical releases as of late last week. If you upgraded your proof-of-work node prior to these releases, you must upgrade again<\/strong> to remain in consensus after London.<\/em><\/p>\n

The London fork is expected between August 3-5, 2021. There is no time like the present — upgrade now!<\/em><\/strong><\/p>\n

<\/g><\/svg><\/a>The Merge — checklist and draft EIP<\/h2>\n

Mikhail, Tim, and I put together a public facing “Merge Mainnet Readiness Checklist”<\/a>. This documents the various tasks required to get us from here to the Merge, aiding both client team coordination as well as providing a better view into progress for the community. Note that this list is pretty high level<\/em>, and that it’s meant to serve as an aid. Much of the more nitty gritty organization and communication around each point happens on calls, discord chats, independent repos, etc.<\/p>\n

Additionally if you want to get more technical, Mikhail, Vitalik, and I just released a Merge specification for the execution-layer perspective in the form of a draft EIP<\/a>. This doesn’t contain any major surprises but is a critical step toward the next wave of Merge development!<\/p>\n

<\/g><\/svg><\/a>Altair progress<\/h2>\n

Altair, the first major upgrade of the Beacon Chain, is making excellent progress after the launch of two small devnets primarily composed of nodes and validators run by client teams. With these first devnets, we moved from alpha to beta releases as the feature-set has been vetted by all teams with all expected refinements now in the spec — v1.1.0-beta.2<\/span> Mach’acuay<\/a>.<\/p>\n

This week, we expect to see another devnet launch followed by discussions for picking a date to fork Pyrmont, a long-standing beacon chain testnet. This will bring in many more node operators at much larger scale and set the stage for a final wave of testing and a selection of a mainnet target launch date.<\/p>\n

For more background on the what, why, and how of Altair, check out this excellent set of Altair PEEPanEIPs by the Ethereum Cat Herders:<\/p>\n

    \n
  1. #34: Altair – Accounting reform with Alex Stokes<\/a><\/li>\n
  2. #35: Altair Beacon chain upgrade with Vitalik and Danny<\/a><\/li>\n
  3. #38: Altair in Teku with Adrian Sutton<\/a><\/li>\n<\/ol>\n

    Lastly, prepping the Beacon Chain codebases for their first upgrade has been a fun, yet challenging task. Here’s a huge shoutout for all the excellent work by client teams to get us near this major milestone \ud83d\ude80<\/p>\n<\/div>\n


    \n
    Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    tl;dr Upgrade for London, yes you! The hotly anticipated upgrade to Ethereum mainnet — London — has a fork block scheduled, and mainnet client releases are out. As mentioned before, to allow for validator deposits, the beacon chain validators come to consensus on the state of the proof-of-work chain and process deposits sequentially from there. […]<\/p>\n","protected":false},"author":6,"featured_media":17933,"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-18125","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\/18125","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=18125"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/18125\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/17933"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=18125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=18125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=18125"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=18125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}