The Merge is now behind us and protocol developers are making (record?) In the last few months, protocol developers have made significant progress in a (record?) Recently, there have been significant improvements in a variety of areas including withdrawing, danksharding and EOF.
To help advance each of these threads and run through another series of Shapella Stress Tests, the client team gathered in Austria for a seven-day interop event: Edelweiss🏔️
Contrary AmphoraUnlike the previous event which was centered on The Merge alone, this one had two tracks, each focusing on Shapella or ProtoDanksharding upgrades. A number of breakout sessions were held to focus on other problems. Here is a brief overview of what was accomplished, as well as links to artifacts from the workshops & ongoing discussion threads.
Shapella
The week started with a Shanghai/Capella shadow fork on the mainnet. The network was flooded with withdrawal credential updates messages, which revealed performance problems on the network. This led to the design of a new consensus-layer queueing system to process the messages.
Throughout the week additional devnets have been launched and stressed tested with large amounts credential updates and withdrawals. The client implementations were ready to go for the launch of the newly launched Zhejiang testnet.
Shapella upgrade Sepolia, Goerli and other testnets in Zhejiang will be upgraded if Zhejiang goes smoothly next!
(Proto)Danksharding
The primary EIP 4844 interop objective was to launch an EIP 4844 development network for all clients. On Friday, all clients except one were synching on the network.
A number of design discussions took place throughout the week. transaction pool design proposal. Allowing questions “blobless” 4844 transactions: if and when? blocks & blobs should be coupled for gossip The topic of how to encrypt these transactions has been discussed extensively on the last week’s AllCoreDevs Execution Layer call.
Over the years, next Teams hope to launch a new developer network in the next few days after finalizing all spec changes that resulted from these discussions.
EVM Object File Format (EOF).
After being conditionally approved and then removed from Shanghai EOF was a topic where opinions on the best course of action diverged most.
Whether EOF should ban code introspectionYou can even aim for a quick deployment. Only a few people know how to pronounce the word “only” During the week, we discussed whether or not to ever go live with L2s.
Although no concrete specifications were developed, the team now has a shared understanding and options for the future. The workshop did not produce any concrete specifications, but the teams have gained a better understanding of design space and possible paths to take. EOF breakout rooms Resumés next Continue this conversation next week!
All Other Things
Aside from these three topics, teams discussed the future of light clients on the network, how the EL & CL specs processes could converge (and potentially carve out ERCs from other EIPs), launched a new Verkle Trie testnetYou can make a proposal. SSZ encode EL transactionsDiscussed changing the validator EL->CL deposit mechanicsThe. and started a Capella annotated spec!
Next Steps
Client teams are already discussing the Shapella testnet timelines less than one week after the event. In the coming weeks, keep an eye on this blog as well as client repositories to see announcements!
Expect to see design discussions for other initiatives, such as EIP 4844, EOF and SSZ in the next few weeks. Prototype implementations will follow.
Shapella will soon be here and Dencun can clearly be seen on the horizon🌅
“This article is not financial advice.”
“Always do your own research before making any type of investment.”
Source: blog.ethereum.org