{"id":18083,"date":"2026-03-08T18:23:07","date_gmt":"2026-03-08T18:23:07","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/08\/finalized-no-31-ethereum-foundation-blog\/"},"modified":"2026-03-08T18:23:07","modified_gmt":"2026-03-08T18:23:07","slug":"finalized-no-31-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/08\/finalized-no-31-ethereum-foundation-blog\/","title":{"rendered":"Finalized no. 31 | Ethereum Foundation Blog"},"content":{"rendered":"


\n
<\/p>\n

\n

This issue of Finalized<\/em> is dedicated to the contextualization of a recently published paper<\/a> describing three possible attacks on Ethereum’s proof-of-stake algorithm.<\/p>\n

tl;dr<\/p>\n

\n

These are serious attacks with a formally-analyzed, technically-simple mitigation. A fix will be rolled out prior to the Merge and will not<\/em> delay Merge timelines.<\/p>\n<\/blockquote>\n

<\/g><\/svg><\/a>Forkchoice attacks, mitigations, and timelines<\/h2>\n

There has recently been quite a bit of chatter around a newly published paper<\/a> co-authored by a team at Stanford and some EF researchers. This paper made public three liveness and reorg attacks on the beacon chain’s consensus mechanism without<\/em> providing any mitigations or any contextualization of what this means for Ethereum’s coming Merge upgrade. The paper was released in an effort to better facilitate review and collaboration before introducing fixes on mainnet. It failed however to provide context on impact and mitigations. This left room for uncertainty in ensuing discussions.<\/p>\n

Let’s get to the bottom of it.<\/p>\n

<\/g><\/svg><\/a>Yes, these are serious attacks \u2694\ufe0f<\/h3>\n

First of all let us make clear, these are serious<\/em> issues that, if unmitigated, threaten the stability of the beacon chain. To that end, it is critical that fixes are put in place prior to the beacon chain taking over the security of Ethereum’s execution layer at the point of the Merge.<\/p>\n

<\/g><\/svg><\/a>But with a simple fix \ud83d\udee1<\/h3>\n

The good news is that two simple fixes to the forkchoice have been proposed — “proposer boosting” and “proposer view synchronization”. Proposer boosting has been formally analyzed by Stanford researchers (write-up to follow shortly), has been spec’d since April<\/a>, and has even been implemented<\/a> in at least one client. Proposer view synchronization<\/a> also looks promising but is earlier in its formal analysis. As of now, researchers expect proposer boosting to land in the specs due to it’s simplicity and maturity in analysis.<\/p>\n

At a high level, the attacks from the paper are caused by an over-reliance on the signal from attestations \u2014 specifically for a small number of adversarial attestations to tip an honest view in one direction or another. This reliance is for a good reason — attestations almost entirely eliminate ex post<\/a> block reorgs in the beacon chain — but these attacks demonstrate that this comes at a high cost — ex ante<\/a> reorgs and other liveness attacks. Intuitively, the solutions mentioned above tune the balance of power between attestations and block proposals rather than living at one end of the extreme or the other.<\/p>\n

Caspar did an excellent job succinctly explaining both the attacks and proposed fixes. Check out this twitter thread<\/a> for the best tl;dr you’ll find.<\/p>\n

<\/g><\/svg><\/a>And what about the Merge? \u26d3<\/h3>\n

Ensuring a fix is in place before the Merge is an absolute must<\/strong>. But there is a fix, and it is simple to implement.<\/p>\n

This fix targets only the forkchoice and is therefore congruous with the Merge specs as written today. Under normal conditions, the forkchoice is the exact same as it is now, but in the event of attack scenarios the fixed version helps provide chain stability. This means that rolling out a fix does not<\/em> introduce breaking changes or require a “hard fork”.<\/p>\n

Researchers and developers expect that by the end of November, proposer boosting will be integrated formally into the consensus specs, and that it will be live on the Merge testnets by mid-January.<\/p>\n

Lastly, I want to give a huge shoutout to Joachim Neu, Nusret Ta\u015f, and David Tse — members of the Tse Lab<\/a> at Stanford — as they have been invaluable<\/strong> in not only identifying, but remedying, the critical issues discussed above<\/em> \ud83d\ude80<\/p>\n<\/div>\n