{"id":18165,"date":"2026-03-11T02:56:34","date_gmt":"2026-03-11T02:56:34","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/11\/finalized-no-25-ethereum-foundation-blog\/"},"modified":"2026-03-11T02:56:34","modified_gmt":"2026-03-11T02:56:34","slug":"finalized-no-25-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/11\/finalized-no-25-ethereum-foundation-blog\/","title":{"rendered":"Finalized no. 25 | Ethereum Foundation Blog"},"content":{"rendered":"


\n<\/p>\n

\n

tl;dr<\/p>\n

<\/g><\/svg><\/a>Rayonism\u2600\ufe0f, hacking the Merge together<\/h2>\n

This week, protolambda and others released plans for Rayonism<\/a>, an ambitious month-long hack to create Merge devnets based on current specs with a stretch goal of adding sharding to these devnets along with L2 rollup integrations.<\/p>\n

The primary motivation is to unite development around a unified Merge spec to onboard all client teams firmly into the Merge design and process so that an informed decision on the Merge roadmap can be agreed upon in the coming months. That, and have a little bit of fun \ud83d\ude42<\/p>\n

\"\"<\/p>\n

In addition to Rayonism, Merge specs<\/a> and design documents<\/a> are making great progress. Huge shout-out to Mikhail and to the many reviewers and contributors pushing this along!<\/p>\n

Read more about Rayonism here<\/a> and join us in the Eth R&D discord<\/a> #rayonism\u2600\ufe0f channel to get involved!<\/p>\n

<\/g><\/svg><\/a>blst<\/span> security advisory<\/h2>\n

Yesterday, Supranational released a security advistory<\/a> for the blst<\/span> BLS library that is currently in use in production by all beacon chain clients today.<\/p>\n

During the course of differential fuzzing of the blst library by Guido Vranken<\/a>, he discovered that blst can produce the incorrect result for some input values in the inverse function. This was patched in a blst<\/span> release<\/a> three weeks go and has been released into all beacon chain clients.<\/p>\n

Although there is currently no known practical exploit of this issue, it is advised that everyone running beacon chain clients upgrade to the latest version in case an exploit is uncovered. Similarly, if you use blst<\/span> in your project, we highly recommend bumping to the latest version as soon as possible.<\/p>\n

[Note: Teku was not running an affected version of blst<\/span>, but they have some juicy optimizations recently so you might as well upgrade anyway]<\/em><\/p>\n

You can read more about this issue in the public security advisory<\/a> on the blst<\/span> repo.<\/p>\n

<\/g><\/svg><\/a>Beacon Chain security+testing RfP<\/h2>\n

Reminder! There is an outstanding Beacon Chain security+testing RfP<\/a>.<\/p>\n

The EF is looking for any proposals that further the security and robustness of the Beacon Chain and the upcoming merge (migration from PoW to PoS). Live network analysis, formal verification, client load testing, new consensus vectors — just to name a few potential paths.<\/p>\n

Get creative! Given you and your team’s skillset, there is likely a valuable way to contribute to the security of this system.<\/p>\n

Proposals are due April 20th<\/em><\/strong> \ud83d\ude80<\/p>\n<\/div>\n