Nyota Interop Milestones ✨


Context

The purpose of Nyota is to work together on Pectra, Verkle & PeerDAS ✨

By bringing together the various client, testing and research teams involved in these efforts, we can accelerate progress on finding+fixing cross-client issues, finalizing specs, and getting these upgrades shipped.

As such, the three high-level goals for Nyota are:

  1. Pectra: all-client-pairs devnet running smoothly
  2. Verkle: multi-client devnet with a finalized gas schedule and pre- & post-transition full sync
  3. PeerDAS: devnet serving & receiving data at head, and (stretch goal!) sampling during sync

To hit these goals and take advantage of Nyota’s high-bandwidth setting, client teams should ideally have Pectra implementations completed and ready to test in a cross-client setting prior to the workshop. Additionally, EL & CL teams should have at least one attendee caught up on Verkle & PeerDAS respectively. More info in the Preparations section below.

With hindsight, past interop events like Amphora 🏺 and Edelweiss 🏔️ enabled us to ship each of The Merge, Shapella and Dencun 3-6 months earlier than we otherwise would. In other words, at their best, these events give us over 1 month of “async progress time” per day!

Teams showing up with advanced implementations & high context will allow us to immediately dive deep into the thorniest issues and tighten the feedback loops around finding issues, fixing them, and testing fixes across all clients.

Nyota Interop ✨

Agenda

Pectra Milestones

Verkle Milestones

PeerDAS Milestones

Preparations

Teams should aim to complete these milestones prior to interop

Pectra

Verkle

PeerDAS

See https://github.com/ethereum/consensus-specs/issues/3686
Test vectors: https://github.com/ethereum/consensus-spec-tests/releases/tag/v1.5.0-alpha.1