Highlights of Ethereum Consensus Layer meeting 90

Concerns over TheMerge, TTD for Sepolia, and other agendas were raised in Consensus-layer Call 90.

Highlights of Ethereum Consensus Layer meeting 90



Deadlock resulted from the two being stuck waiting for each other as a result of an Erigon bug and a minor Teku problem. It is suggested that the specification be modified to indicate that the consensus client should retry a timed-out. Mikhail has not yet submitted a PR for review. Teku has now been updated to retry FCU timeout calls. As a result, Erigon's problem is now solved.

How do optimistically configured consensus clients behave after a restart? What transpires with beacon blocks whose content has a NOT VALIDATED state once the CL client is restarted? Is the status of NOT VALIDATED persistent in any case, or is it possible that beacon blocks with NOT VALIDATED payloads are not persistent and the CL client tries to remove them from the wire if necessary?

In the unlikely scenario that the consensus client does not resend invalid payloads, data availability problems can arise. But Danny believes that this is most likely not the case. PaulH claims that upon restart, Lighthouse does not repeat any blocks.

Mainnet-Shadow-Fork 8

TTD is expected to be reached around Tuesday, Nodes are syncing. Mainnet-Shadow-Fork 7 is about to be deplored.


Sepolia Merge has been announced and TTD has been decided. Although Merge may occur earlier than expected due to some additional mining on the chain, everything is prepared in either scenario. For 16 epochs after the Merge, they will configure Sepolia relay to return 205 errors. The builder and relay are available on Sepolia for testing.

Gray Glacier

Gray Glacier hard fork was successful and the difficulty bomb will now be delayed by around 700,000 blocks or 100 days. The bad chain only has one block or less than 0.2 percent of the total hash rate. Providers of equipment have not reported any problems.

MEV-Boost (Adding signature to getHeader)

The block auction dynamics are thrown off since validators do not currently authenticate to relays, as a result, the auction is open. That would be a better option if there was a sealed-bid auction. The drawback is that validators would have to sign in order to prove their identity to the relay before getting access to the bids. A validator will probably select relays that provide smaller increments in order to obtain the best bids despite the overhead.

Other Reads


Disclaimer: The information contained on this web page is for education purposes only. Readers are suggested to conduct their own research, review, analyze and verify the content before relying on them.

To publish press releases, project updates, and guest posts with us, please email at contact@etherworld.co.

Subscribe to EtherWorld YouTube channel for ELI5 content.

Share if you like the content. Support us at Gitcoin

You've something to share with the blockchain community, join us on Discord!

Follow us at Twitter, Facebook, LinkedIn, and Instagram

Share Tweet Send
You've successfully subscribed to EtherWorld.co
Great! Next, complete checkout for full access to EtherWorld.co
Welcome back! You've successfully signed in
Success! Your account is fully activated, you now have access to all content.