{"id":17699,"date":"2026-02-26T19:42:01","date_gmt":"2026-02-26T19:42:01","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/02\/26\/nyota-interop-recap-%e2%9c%a8-ethereum-foundation-blog\/"},"modified":"2026-02-26T19:42:01","modified_gmt":"2026-02-26T19:42:01","slug":"nyota-interop-recap-%e2%9c%a8-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/02\/26\/nyota-interop-recap-%e2%9c%a8-ethereum-foundation-blog\/","title":{"rendered":"Nyota Interop Recap \u2728 | Ethereum Foundation Blog"},"content":{"rendered":"


\n<\/p>\n

\n

Last week, Ethereum client, testing and research teams from around the world gathered together for a week of intense work on the Pectra network upgrade, PeerDAS and the Verge.<\/p>\n

Similarly to previous events like Edelweiss \ud83c\udfd4\ufe0f<\/strong><\/a> or Amphora \ud83c\udffa<\/strong><\/a>, the focus of the Nyota \u2728<\/strong> interop was achieving multi-client interoperability across the different technical tracks.<\/p>\n

In addition to this, Nyota was preceded with a first of its kind public event: Frontiers Africa<\/a>, where core devs & researchers spent the day meeting & exchanging with builders from across the region.<\/p>\n

<\/g><\/svg><\/a>Frontiers Africa<\/h2>\n

Inspired by the impactful trips<\/a> that borderless.africa<\/a> organized in Africa last year, the continent quickly became a top contender to host interop. To maximize the impact of having over 100 core Ethereum contributors in one of the places that can most benefit from it, we organized a one day community event right before interop: Frontiers Africa.<\/p>\n

The purpose of the event was to allow L1 maintainers and local builders to learn from each other. After a few morning panels, the agenda was filled with breakout sessions for attendees to take part in two-way conversations on topics ranging from the Ethereum roadmap, to the onboarding journey for core contributors, how to build applications for mass adoption on the African continent and how to bridge the African and global communities.<\/p>\n

\"\"<\/p>\n

Frontiers Africa had over 350 local attendees along with interop participants. The event hopefully laid the groundwork for more, larger, Ethereum-focused events taking place across Africa!<\/p>\n

<\/g><\/svg><\/a>Nyota \u2728<\/h2>\n

This year’s interop event focused on three main technical tracks: Pectra, PeerDAS and Verkle. In addition to these, the teams also made progress on EOF, SSZ, History Expiry and more.<\/p>\n

<\/g><\/svg><\/a>Pectra Devnet 0<\/h3>\n

The main focus of Nyota was cross-client interoperability on devnet-0<\/a>. Teams were expected to come to interop with full implementations and spend the week gradually building towards multi-client devnets running smoothly.<\/p>\n

On the first day, we saw many 1:1 devnets, where specific EL:CL pairs could run together locally. Quickly, more complex devnets started appearing, with a 5×5 one launching mid-week! While in past interop events this would have represented all client combinations, Nyota had two new client teams join for the first time: Grandine<\/a> and Reth<\/a>.<\/p>\n

By the end of the week, all but one client was running on devnet-0<\/span>, and external dependencies such as relays were getting tested. As a final test on the last evening of the event, an execution layer-triggered withdrawal was sent over the network, with the validator successfully exiting and the network finalizing smoothly!<\/p>\n

<\/g><\/svg><\/a>Verkle<\/h3>\n

Prior to interop, Verkle contributors were expected to join the Kaustinen testnet<\/a>. While this wasn’t achieved by all teams ahead of 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.<\/p>\n

In addition to implementation work, one key goal for the Verkle track was to try and resolve many outstanding spec issues. The various sessions on the topic resulted in a draft PR<\/a> to the EIP for broader discussion before finalizing the changes.<\/p>\n

<\/g><\/svg><\/a>PeerDAS<\/h3>\n

Last but not least, the PeerDAS track is likely the one where the most progress was made throughout the interop. At the start of the week, only two of the consensus layer clients had partial implementations.<\/p>\n

By Friday, all six teams could distribute and receive data to subnets, all but one could serve the data over RPC, multi-client devnets had been stood up, and some teams had started working on sync integrations!<\/p>\n

<\/g><\/svg><\/a>Everything Else<\/h3>\n

In addition to the core technical tracks, teams made progress on a range of other initiatives, such as:<\/p>\n

…and even an entire SSZ Technical Track<\/a>!<\/p>\n

\"\"<\/p>\n

<\/g><\/svg><\/a>Next Steps<\/h2>\n

Expect the notes and draft PRs coming out of Nyota to be refined into formal specs & proposals over the next few weeks. While many ideas were discussed throughout the week, any changes to the Ethereum protocol will be brought up, as always, on AllCoreDevs calls<\/a>.<\/p>\n

Over the next few weeks, teams expect to finalize the scope of the Pectra network upgrade and continue testing their implementations. Once this process has completed, an announcement will be made for the upgrade deployment on existing testnets.<\/p>\n

\n

Thank you to everyone who participated in interop and made it both an incredibly productive and fun week. Special shout out to the EthPandaOps, specs and testing teams whose work enabled everyone else to hit the ground running. For Amphora \ud83c\udffa<\/strong><\/a>, our interop target was to stand up a single devnet by the end of the week. This time, we launched over 100!<\/p>\n<\/div>\n


\n
Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Last week, Ethereum client, testing and research teams from around the world gathered together for a week of intense work on the Pectra network upgrade, PeerDAS and the Verge. Similarly to previous events like Edelweiss \ud83c\udfd4\ufe0f or Amphora \ud83c\udffa, the focus of the Nyota \u2728 interop was achieving multi-client interoperability across the different technical tracks. […]<\/p>\n","protected":false},"author":6,"featured_media":17700,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-17699","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17699","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=17699"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17699\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/17700"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=17699"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=17699"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=17699"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=17699"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}