Skip to content

Edelweiss Interop Recap | Ethereum Foundation Blog

The Merge is now firmly behind us, with protocol builders making (report?) strides up to now few months. Withdrawals, Dansharding, EOF, Workal Trie, Historical past Expiry, SSZ and extra have all seen important progress lately!

To assist advance every of those threads, and run Shpela by way of one other collection of stress exams, members of the client staff gathered in individual for a week-long interop occasion in Austria: Edelweiss 🏔️

Completely different pitcher, whose sole focus was on The Merge, featured two main tracks on the occasion, specializing in the Shapella and ProtoDunksharding community upgrades, respectively. A number of breakout classes had been additionally held to debate different open issues. This is a quick description of what was achieved, in addition to hyperlinks to artifacts from the workshops and ongoing discussions.


The week began with the Shanghai/Capella mainnet shadow fork. Flooding the community with withdrawal credential replace messages revealed efficiency points on the community, and led to a separate consensus-layer queue design to course of these messages.

All through the week, extra devnets had been launched and stress examined with a considerable amount of credential updates, withdrawals, and even dangerous blocks. On the finish of the week shopper implementation hardened and able to fork over newly-launched zhejiang testnet,

Assuming that the Shepela improve goes by way of with none points on ZheJiang, the Shepela and Goerli testnets will likely be upgraded subsequent!

(proto) dansharding

The principle EIP-4844 interop aim was the launch of an all-client EIP-4844 DevNet. As of Friday, all purchasers besides one had been syncing over the community!

A number of design discussions additionally passed off in the course of the week, one in every of which was transaction pool design proposal, Questions associated to permitting “blobless” 4844 transactions, what and the way Blocks and Blobs should be mixed for chatter And the right way to encode these transactions was mentioned extensively and got here to the fore final week AllCoreDevs execution layer name,

Over the following few weeks, the groups anticipate to finalize all particular modifications ensuing from these discussions and launch a brand new DevNet.

EVM Object Format (EOF)

After being conditionally accepted after which faraway from Shanghai, the EOF was one of many subjects the place opinion differed most about one of the simplest ways ahead.

Ought to EOF restriction code introspectionpurpose for minimal deployment as quickly as potential, and even Solely In the course of the week the L2s had been mentioned going dwell anytime.

No concrete specifics emerged from the workshop, however the groups now have a shared understanding of the design area and potential paths ahead. eof breakout room Verify again subsequent week to proceed this dialog!

every little thing else

Along with these three subjects, the groups mentioned the way forward for light-weight purchasers on the community, how the EL and CL spec processes might (and sure will) change. Create ERC from different EIP), launched a brand new workl attempt testnetmade a proposal for SSZ encode EL transactionmentioned validator EL->CL altering deposit mechanicsand even began capella annotated spec,

subsequent steps

Lower than per week after the occasion, buyer groups began discussing the Shepela timelines for the testnet. Regulate this weblog in addition to the shopper repository for bulletins within the coming weeks!

For different efforts comparable to EIP-4844, EOF, SSZ, it’s anticipated to see lively design discussions within the coming weeks, adopted by prototype implementation.

Shapela is sort of right here, and Denkun is obvious on the horizon 🌅

Ready to get a best solution for your business?