--- tags: nyota --- # Nyota Interop Milestones ✨ [toc] --- # 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 4. **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](#preparations) section below. With hindsight, past interop events like [Amphora 🏺](https://blog.ethereum.org/2021/10/15/amphora-merge-milestone) and [Edelweiss 🏔️](https://blog.ethereum.org/2023/02/07/edelweiss-interop-recap) 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](https://docs.google.com/spreadsheets/d/1uBxWGHuWipTBdbzV019YPcYAOMJqJDkU1UkAI_Qarrc/edit?usp=sharing) ### [Pectra Milestones](https://notes.ethereum.org/@timbeiko/pectra-interop-milestones) ### [Verkle Milestones](https://notes.ethereum.org/@gballet/verke_interop_milestones) ### [PeerDAS Milestones](https://notes.ethereum.org/@ethpandaops/peerdas-devnet-0) ## Preparations *Teams should aim to complete these milestones prior to interop* ### Pectra - [ ] Full [devnet-0](https://notes.ethereum.org/@ethpandaops/pectra-devnet-0) implementations ### Verkle - [ ] Joining the [kaustinen testnet](https://kaustinen-testnet.ethpandaops.io) ### 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 - [ ] Pass PeerDAS KZG tests - Justin T: We now have EIP-7594 functions for all the bindings (including Python). And they are all passing the reference tests. 🔥 - [ ] Pass EIP-7594 `merkle_proof/single_merkle_proof/BeaconBlockBody` tests - this is for verifying `get_data_column_sidecars` implementation - [ ] Pass EIP-7594 `networking/get_custody_columns` tests
Last changed by  
 
Tim Beiko
649

Read more

Pectra Interop Milestones

Useful links: Nyota Interop Milestones Verkle Interop Milestones PeerDAS Interop Milestones Nyota Agenda Interop Milestone Tracker :::info All milestones in this document are based on the pectra-devnet-0 specs.

5/22/2024
Besu Client Incentive Program - August 2023 Changes

Important note: this program superceeds any previous version of the Besu Client Incentive Program, including the one publicly shared on the Hyperledger Besu Wiki. [toc] Context The Ethereum Foundation's Client Incentive Program aims to incentivize client teams to build performant software for use on the Ethereum mainnet. Generally, client implementation are maintained by a single organization, and CIP grants have been offered to the organizations who maintain these clients. Due to its different maintainership structure, Hyperledger Besu's program was designed to accomodate a more diverse set of contributors. A version of the Hyperledger Besu CIP refleting this is available here.

10/14/2023
EIP-4788 Contract Audit Request

Context The Ethereum Foundation is soliciting proposals for an audit of the smart contract bytecode to be deployed as part of EIP-4788. A recent specification change, implemented in this pull request, has changed the contract storing Beacon Roots from a precompile to a regular smart contract, which would either be deployed prior the EIP's activation or as part of its associated network upgrade. Audit Requirements The audit should focus exclusively on the smart contract bytecode used to store Beacon Roots, referenced in the pull request above. It should not encompass all of EIP-4788 (for example, how the beacon roots are passed from the EL to the CL), or client implementations of the EIP, including their interactions with the contract. An etk implementation of the contract can be found in this repository: https://github.com/lightclient/4788asm

8/10/2023
1/24 4844-devnet breakout

Edelweiss Devnet Status Docs Overview Started with geth (CB prototype), prysm, lighthouse, lodestar If you want to be a validator, let Mofi know Teku would like to join

1/24/2023
Read more from Tim Beiko
Published on HackMD