Now that The Merge is a thing of the past, protocol developers have been advancing across a (record?) number of domains in recent months. Significant strides have been made in areas like withdrawals, danksharding, EOF, verkle tries, history expiry, SSZ, and more!
To propel these endeavors forward and conduct another round of Shapella stress tests, client team members convened for a week-long interop event in Austria: Edelweiss 
Differing from Amphora, which solely concentrated on The Merge, this event featured two principal tracks focused on the Shapella and ProtoDanksharding network upgrades, respectively. Several breakout sessions were organized to explore additional challenges. Below is a summary of what was achieved, along with links to artifacts from the workshops & ongoing discussions.
Shapella
The week kicked off with a Shanghai/Capella mainnet shadow fork. Overloading the network with withdrawal credential update messages uncovered performance problems and prompted a redesign of the consensus-layer queueing system for processing these messages.
As the week progressed, more devnets were initiated and stress-tested with substantial volumes of credential updates, withdrawals, and even faulty blocks. Client implementations emerged from the week fortified and prepared for the fork on the newly-launched Zhejiang testnet.
Barring any issues with the Shapella upgrade on Zhejiang, the Sepolia and Goerli testnets are next in line for an upgrade!
(Proto)Danksharding
The primary interop aim for EIP-4844 was to launch an all-client EIP-4844 devnet. By Friday, all but one client were synchronized on the network!
Throughout the week, numerous design conversations stemmed from a transaction pool design proposal. In-depth discussions involved whether to permit “blobless” 4844 transactions, considerations for how blocks & blobs should interact for gossip and approaches to encoding these transactions, all of which were raised during last week’s AllCoreDevs Execution Layer call.
In the upcoming weeks, teams aspire to finalize all specification changes resulting from these discussions and initiate a new devnet.
EVM Object Format (EOF)
After being conditionally accepted and then removed from Shanghai, EOF emerged as a highly debated topic regarding the most effective way forward.
Discussions revolved around whether EOF should prohibit code introspection, pursue a minimal deployment as soon as possible, or even only be implemented on L2s.
Although no definitive specification emerged from the workshop, teams now possess a mutual understanding of the design landscape and possible future directions. The EOF breakout rooms will resume next week to persist in this dialogue!
Everything Else
Beyond these three focal points, teams explored the future of light clients on the network, the convergence of EL & CL specs processes (and potential plans to distinguish ERCs from other EIPs), launched a new Verkle Trie testnet, proposed to SSZ encode EL transactions, discussed modifying the validator EL->CL deposit mechanics, and even initiated a Capella annotated spec!
Next Steps
Less than a week after the event, client teams have started discussing timelines for Shapella on testnets. Stay tuned to this blog, as well as to clients’ repositories, for updates in the following weeks!
For other initiatives, such as EIP-4844, EOF, and SSZ, expect to see active design discussions unfolding in the next few weeks, leading up to prototype implementations.
Shapella is on the horizon, and Dencun is clearly visible ahead 
Dutch
English
French
German
Greek
Italian
Portuguese
Russian
Spanish