{"id":6965,"date":"2025-01-05T07:53:28","date_gmt":"2025-01-05T06:53:28","guid":{"rendered":"https:\/\/wsj-crypto.com\/?p=6965"},"modified":"2025-01-05T07:53:28","modified_gmt":"2025-01-05T06:53:28","slug":"ethereum-foundations-milestone-unveiling-version-25","status":"publish","type":"post","link":"https:\/\/wsj-crypto.com\/index.php\/2025\/01\/05\/ethereum-foundations-milestone-unveiling-version-25\/","title":{"rendered":"Ethereum Foundation’s Milestone: Unveiling Version 25"},"content":{"rendered":"

<\/p>\n

\n

tl;dr<\/p>\n


\n<\/p>\n

Rayonism\u2600\ufe0f, collaborating on the Merge<\/h2>\n

<\/p>\n

This week, protolambda and others unveiled plans for Rayonism<\/a>, an ambitious month-long initiative aimed at developing Merge devnets based on current specifications, with an additional goal of incorporating sharding in these devnets alongside L2 rollup integrations.<\/p>\n

<\/p>\n

The main objective is to consolidate development around a standardized Merge spec to bring all client teams thoroughly into the Merge design and workflow, ensuring that a well-informed decision regarding the Merge roadmap can be reached in the upcoming months. Additionally, it’s about enjoying the process a little! \ud83d\ude42<\/p>\n

<\/p>\n

\n

<\/p>\n

Besides Rayonism, Merge specifications<\/a> and design documents<\/a> are advancing well. A massive shout-out to Mikhail and the numerous reviewers and contributors who are driving this forward!<\/p>\n

<\/p>\n

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

<\/p>\n

blst<\/span> security announcement<\/h2>\n

<\/p>\n

Yesterday, Supranational issued a security advisory<\/a> for the blst<\/span> BLS library, which is currently utilized in production by all beacon chain clients today.<\/p>\n

<\/p>\n

During the differential fuzzing process of the blst library conducted by Guido Vranken<\/a>, it was found that blst could yield incorrect outcomes for certain input values within the inverse function. This issue was addressed in a blst<\/span> release<\/a> that came out three weeks ago and has been incorporated into all beacon chain clients.<\/p>\n

<\/p>\n

While there is no known practical exploit of this issue currently, it is recommended that all running beacon chain clients upgrade to the latest version in case any exploit is found. Similarly, if you are utilizing blst<\/span> in your project, we strongly advise updating to the latest version as soon as feasible.<\/p>\n

<\/p>\n

[Note: Teku was not utilizing a compromised version of blst<\/span>, but they have recently implemented some valuable optimizations, so you should consider upgrading regardless]<\/em><\/p>\n

<\/p>\n

Additional details regarding this issue can be found in the public security advisory<\/a> available on the blst<\/span> repository.<\/p>\n

<\/p>\n

Beacon Chain security+testing Request for Proposal<\/h2>\n

<\/p>\n

Reminder! There is a current Beacon Chain security+testing Request for Proposal<\/a>.<\/p>\n

<\/p>\n

The EF is seeking any submissions that enhance the security and resilience of the Beacon Chain and the impending merge (transition from PoW to PoS). Live network assessments, formal verification, client load evaluation, new consensus mechanisms — just to mention a few potential avenues.<\/p>\n

<\/p>\n

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

<\/p>\n

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