Edelweiss Interop Recap

With The Merge present firmly down us, protocol developers person been making advancement crossed a (record?) fig of areas implicit the past fewer months. Withdrawals, danksharding, EOF, verkle tries, past expiry, SSZ and much person each seen important advancement recently!

In bid to assistance determination each of these threads forward, and to tally done 1 much bid of Shapella accent tests, lawsuit squad members gathered successful idiosyncratic for a week-long interop lawsuit successful Austria: Edelweiss 🏔️

Unlike Amphora, which had a singular absorption connected The Merge, this lawsuit had 2 large tracks, focused connected the Shapella and ProtoDanksharding web upgrades respectively. Several breakout sessions were besides held to dive into different unfastened problems. Here is simply a little overview of what was accomplished, arsenic good arsenic links to artifacts from the workshops & ongoing treatment threads.

Shapella

The week began with a Shanghai/Capella mainnet shadiness fork. Flooding the web with withdrawal credential update messages revealed show issues connected the network, and led to a antithetic consensus-layer queueing plan to process these messages.

Throughout the week, further devnets were launched and accent tested with ample amounts of credential updates, withdrawals, and adjacent atrocious blocks. Client implementations ended the week hardened and acceptable for the fork connected the newly-launched Zhejiang testnet.

Assuming the Shapella upgrade happens without contented connected Zhejiang, the Sepolia and Goerli testnets volition beryllium upgraded next!

(Proto)Danksharding

The main EIP-4844 interop extremity was the motorboat of an all-client EIP-4844 devnet. By Friday, each but 1 lawsuit were syncing connected the network!

Several plan discussions besides took spot during the week, stemming from a transaction excavation plan proposal. Questions astir allowing "blobless" 4844 transactions, if and however blocks & blobs should beryllium coupled for gossip and however to encode these transactions were discussed extensively and surfaced connected past week's AllCoreDevs Execution Layer call.

Over the adjacent fewer weeks, teams anticipation to finalize each spec changes resulting from these discussions and motorboat a caller devnet.

EVM Object Format (EOF)

After having been conditionally accepted and past removed from Shanghai, EOF was 1 of the topics wherever opinions astir the champion way guardant diverged the most.

Whether EOF should ban codification introspection, purpose for a minimal deployment ASAP, oregon adjacent only ever spell unrecorded connected L2s were each discussed during the week.

No factual specification came retired of the workshop, but teams present person a shared knowing of the plan abstraction and imaginable paths forward. The EOF breakout rooms resumes adjacent week to proceed this conversation!

Everything Else

Aside from these 3 topics, teams discussed the aboriginal of airy clients connected the network, however the EL & CL specs processes could converge (and perchance carve retired ERCs from different EIPs), launched a caller Verkle Trie testnet, enactment guardant a connection to SSZ encode EL transactions, discussed changing the validator EL->CL deposit mechanics, and adjacent started a Capella annotated spec!

Next Steps

Less than a week aft the event, lawsuit teams person begun discussing Shapella timelines for testnets. Keep an oculus retired connected this blog, arsenic good arsenic connected clients' repositories, for announcements successful the coming weeks!

For different efforts, specified arsenic EIP-4844, EOF, SSZ, expect to spot progressive plan discussions successful the coming weeks, starring to prototype implementations afterwards.

Shapella is astir here, and Dencun is wide connected the skyline 🌅