Overview of Edelweiss Interoperability | Ethereum Foundation Blog


With The Merge With the protocol builder’s work finished, they have made remarkable strides in (file?) In the recent months, protocol builders have made progress in a (file?) range of areas. WithdrawalsEOF, danksharding and verkle makes an effort, historical past expiration, SSZ, and more have all advanced significantly in recent years!

In To help move all of these threads forward, another gathering was held. Austria: Edelweiss 🏔️ was chosen for a week-long interop event, and stress tests were conducted by the members of our client team.

Rather than Amphora, single attention was given to The Merge.Two tracks dominated this event, and were centred on the Shapella ProtoDanksharding Community upgrades Additionally, a few other work periods were held to explore other open issues. Here’s a quick summary which includes links to artifacts and ongoing dialogue threads, as well as a summary of the accomplishments.


The The week started with a shadow fork Shanghai/Capella mainnet. Flooding The community that got withdrawal credential replacement messages showed efficiency points and led to an original consensus queue design for dealing with these messages.

Throughout The week saw the launch of more dev networks and stress testing with a variety of credential updates and retirements. On FridayThe week concluded with deployments, and the troops were all set to take the fork in the newly launched vehicles. Zhejiang Check out the community.

Assuming The Shapella It is possible to improve in Zhejiang?, Sepolia Goerli The quality of testnets will continue to improve.


The Primary goal of EIP4844 interoperability for clients was the release of an EIP4844 improvement community. By FridayThere was only one person in the entire community who was synchronizing!

A few Design discussions were also held throughout the week. These talks stemmed from a transaction group design proposal. Questions About allowing “blobleless” 4844 transactions, If and Then Blocks and blobs must be mated to make gossip These transactions and how to code them have been widely discussed and surfaced this week AllCoreDevs execution layer name.

Over In the coming weeks, the groups plan to finalize all the spec adjustments that arise from these talks and create a brand-new improvement community.

EVM Object Format (EOF)

After Acceptance conditionally accepted, but later withheld ShanghaiEOF was a point where opinions diverged the most concerning the best way forward.

If EOF should be prohibition code introspectionTry to implement as little as possible as soon as possible, and as fast as possible. solely The week was marked by mentions of ever going live on the L2 network.

No Concrete specification was not developed in the workshop. However, the groups now have a mutual understanding of the design

Related articles

Recent articles