tl; dr
Rayonism☀️, hacking the Merge together
This week, protolambda and others published plans to rayonisman ambitious month-long hack to create Merge devnets based on current specs with the goal of adding sharding to these devnets along with L2 cumulative integrations.
The primary motivation is to unite development around a unified Merge specification to firmly embed all customer teams in the Merge design and process so that an informed Merge roadmap decision can be agreed upon in the next few months. That, and have some fun 🙂
In addition to rayonism, Merge Specifications Y design documents they are making great progress. A big shout out to Mikhail and the many reviewers and contributors driving this!
Read more about Rayonism here and join us in the Eth R&D Discord #Rayonismo☀️ channel to get involved!
page security notice
Yesterday, Supranational launched a security notice For him page BLS library that is currently in production use by all Beacon Chain customers.
During the course of differential fuzzing of the blst library by guido franken, discovered that blst can produce an incorrect result for some input values in the inverse function. This was patched in a page launching Three weeks pass and it has been released on all Beacon Chain clients.
Although there is currently no known practical exploit of this issue, it is recommended that everyone running Beacon Chain clients update to the latest version in case an exploit is discovered. Similarly, if you use page in your project, we strongly recommend moving to the latest version as soon as possible.
(Note: Teku was not running an affected version of pagebut they have some juicy optimizations recently, so you might as well upgrade anyway)
You can read more about this topic in the public safety notice about him page repository
Beacon Chain security + RfP test
Reminder! there is a standout Beacon Chain security + RfP test.
The EF is looking for proposals that promote the security and robustness of the Beacon Chain and the upcoming merger (PoW to PoS migration). Live network analysis, formal verification, client load testing, new consensus vectors, just to name a few potential paths.
Be creative! Given the skill set of you and your team, there is likely a valuable way to contribute to the security of this system.
Proposals must be submitted by April 20. 🚀
