Last week, Ethereum client, testing, and research teams from around the world came together for an intense week of work on the Pectra, PeerDAS, and Verge network upgrade.
In the same way as in previous events like Edelweiss 🏔️ Or Amphora 🏺the center of the Nyota ✨ Interoperability aimed to achieve multi-client interoperability across the different technical tracks.
In addition to this, Nyota was preceded by a unique public event: Africa Borderswhere developers and researchers spent the day meeting and interacting with builders from across the region.
Africa Borders
Inspired by the impactful trips that Africa without borders Hosted in Africa last year, the continent has quickly become a leading candidate to host the interop. To maximize the impact of having over 100 Ethereum contributors in one of the places that can benefit the most, we hosted a one-day community event just before the interop: Frontiers Africa.
The goal of the event was to allow L1 maintainers and local developers to learn from each other. After a few morning panels, the agenda was filled with breakout sessions that allowed attendees to engage in two-way conversations on topics ranging from Ethereum’s roadmap to the core contributor onboarding journey, building applications for mass adoption on the African continent, and how to connect African and global communities.
Frontiers Africa welcomed over 350 local attendees as well as interoperability participants. The event hopefully laid the foundation for other larger Ethereum-focused events to take place across Africa!
Nyota ✨
This year’s interop event focused on three main technical areas: Pectra, PeerDAS, and Verkle. In addition to these, teams also made progress on EOF, SSZ, History Expiry, and many others.
Pectra Devnet 0
Nyota’s main goal was interoperability between clients on devnet-0Teams were required to interoperate with full implementations and spend the week gradually building smoothly functioning multi-client networks.
On the first day, we saw many 1:1 devnets, where specific EL:CL pairs could work together locally. Soon, more complex devnets started to appear, with a 5×5 devnet launching mid-week! While at previous interop events this would have represented every combination of clients, Nyota saw two new client teams join for the first time: Grandine And Reth.
By the end of the week, all but one client was running on devnet-0and external dependencies such as relays were tested. As a final test, on the last night of the event, a runtime-triggered withdrawal was sent to the network, the validator completed successfully, and the network finalized smoothly!
Verkle
Before interoperability, Verkle contributors had to join the Kaustinen Test Network. While this was not achieved by all teams prior to the event, by the end of the week all but two teams had at least partial implementations, with many also supporting post-transition networks from Genesis.
In addition to the implementation work, one of the key objectives of the Verkle program was to try to resolve many outstanding specification issues. The various sessions on the topic resulted in a PR project to the PEI for a broader discussion before finalizing the changes.
PeerDAS
Finally, the PeerDAS side is probably where the most significant progress has been made throughout interoperability. As of the beginning of the week, only two clients in the consensus layer had partial implementations.
By Friday, all six teams could distribute and receive data to subnets, all but one could stream data via RPC, multi-client development networks had been set up, and some teams had started working on sync integrations!
Everything else
In addition to the basic technical axes, the teams have progressed on a series of other initiatives, such as:
…and even an integer SSZ Technical Course!
Next steps
Expect the notes and draft PRs coming from Nyota to be polished into formal specifications and proposals over the coming weeks. While many ideas were discussed throughout the week, any changes to the Ethereum protocol will be discussed, as always, on AllCoreDevs Calls.
Over the next few weeks, the teams plan to finalize the scope of the Pectra network upgrade and continue testing their implementations. Once this process is complete, an announcement will be made for the upgrade to roll out to existing test networks.
Thanks to everyone who participated in interop and made it an incredibly productive and fun week. Special thanks to the EthPandaOps, Specs, and Test teams whose work got everyone else up and running. For Amphora 🏺Our interoperability goal was to have just one development network up and running by the end of the week. This time, we launched over 100!
