--- tags: nyota --- # Pectra Interop Milestones Useful links: * [Nyota Interop Milestones](/5kHfzDg7SxOYTTdiEKqxNA) * [Verkle Interop Milestones](https://notes.ethereum.org/@gballet/verke_interop_milestones) * [PeerDAS Interop Milestones](https://notes.ethereum.org/@ethpandaops/peerdas-devnet-0) * [Nyota Agenda](https://docs.google.com/spreadsheets/d/1uBxWGHuWipTBdbzV019YPcYAOMJqJDkU1UkAI_Qarrc/edit?usp=sharing) ## Interop Milestone Tracker :::info **All milestones in this document are based on the [pectra-devnet-0](https://notes.ethereum.org/@ethpandaops/pectra-devnet-0) specs.** ::: | Client | M0 | M1 | M2 | M3 | M4 | M✨ | SSZ | |-----|-----|-----|-----|-----|-----|-----|-----| |[Lighthouse](https://github.com/sigp/lighthouse/tree/ef-tests-electra) |:heavy_check_mark: |Nethermind, Besu, Reth | | 🦓 🦍 🐐 🦚 | | |[Teku](https://github.com/Consensys/teku/labels/Epic%20Electra)|:heavy_check_mark:|Nethermind | Nethermind, Besu | 🦓 🦍 🐐 🦚 | | |[Lodestar](https://github.com/ChainSafe/lodestar/issues/6341) |:heavy_check_mark:|Nethermind| | 🦍 🦚 | ||🐼 |[Prysm](https://github.com/prysmaticlabs/prysm/issues/13849)||Nethermind Geth| Nethermind,Geth | 🦚 | |Nimbus | :heavy_check_mark: | | Nethermind, Geth, EthJS | 🦓 🦍 | ||🐼| |Grandine|:heavy_check_mark:|Nethermind Geth| Nethermind,Geth | 🦚 |[Geth](https://github.com/lightclient/go-ethereum/tree/prague-devnet-0)|:heavy_check_mark:|Grandine, Lodestar| | 🦍 🐐 🦚 |[Nethermind](https://github.com/NethermindEth/nethermind/issues/6867) |:heavy_check_mark: | Grandine, Lighthouse, Reth, Teku | Geth, Grandine Besu, Teku| 🦓 🦍 🐐 🦚 | |[Besu](https://github.com/hyperledger/besu/issues/6308) |:heavy_check_mark: |Teku, Lighthouse| Besu, Nethermind, Teku, Geth | 🐐 |Erigon ||||||| 🐼 |[Reth](https://github.com/paradigmxyz/reth/issues/7363)|:heavy_check_mark:|CL: Lighthouse, Grandine, Teku, EL: Nethermind | Lighthouse-Reth & Grandine-Reth, Lighthouse-Reth & Grandine-Nethermind |🦚 | |[EthereumJS](https://github.com/ethereumjs/ethereumjs-monorepo)|:heavy_check_mark:| | | 🦓 🦍 🦚 | *Note: if your team has a Pectra or devnet-0 tracking issue, link it in the **Client** column.* `🦓: Teku, Lighthouse, Nethermind, EthereumJS` `🦍: Lodestar, Teku, Lighthouse, Nethermind, EthereumJS, Geth` `🐐: Besu, Teku, Lighthouse, Nethermind, Geth` `🦚: Lighthouse, Teku, Prysm, Grandine, Lodestar, Nethermind, EthereumJS, Geth, Besu` --- ### M0 --- single client implementation * Full [devnet-0](https://notes.ethereum.org/@ethpandaops/pectra-devnet-0) implementation, passing all static tests. * When complete, add a :heavy_check_mark: in the M0 cell of your client's row. :::warning **Ideally, M0 should be completed before interop!** ::: ### M1 --- 1:1 interop * Run a local devnet with a counterpart client, e.g. an EL client runs with a devnet-0-ready CL, or vice-versa. * When complete, record the counterpart client in the M1 cell of your client's row. * For example, if Teku interops with Nethermind locally, then `Teku[M1]` should read `Nethermind` and `Nethermind[M1]` should read `Teku`. ### M2 --- 2:1 interop * Achieve finalization on a local devnet with another client from each layer. For, e.g. an EL client to achieve M2, at least one other EL client should be running on the same network, even if they both use the same CL.. * When complete, record both other clients in the M2 cell of your client's row. * For example, in a Teku, Nethermind and Besu devnet, `Nethermind[M2]` would read `Teku, Besu`, `Besu[M2]` would read `Nethermind, Teku`, and Teku would remain blank until it interops with another CL. ### M3 --- M:N interop * Achieve finalization on a local devnet with 2+ ELs and 2+ CLs, all with full devnet-0 support * When complete, name the devnet using a Kenya-themed animal emoji (but not 🐘, that's Verkle!), add the emoji-client mapping under the **Interop Milestone Tracker** table, and add the emoji in the M3 cell of each client participating in the devnet. * For example, in a Lodestar, Prysm, Besu and Reth devnet, hypothetically named 🐘 (again, don't use that one :-), each of these clients' M3 cell would have an 🐘 emoji, and under the table, the following reference would be added: `🐘: Lodestar, Prysm, Besu, Reth` ### M4 --- All Client Interop * All clients in the table above are running smoothly together using the `pectra-devnet-0` specs: when done, each team's M4 column will have the Nyota emoji: ✨. * **All teams must be on the devnet for this milestone to be ~~complete~~ M4, otherwise, we'll call it `M(clients interoping/total clients)` --- *LFG!*** ### M✨ --- Relay'd 7002 Finalized Withdrawal * On `devnet-0`, process an externally built block via the relay, in which a 7002 EL withdrawal is triggered. Finalize. If your client makes it through, add a ✨ emoji to its `M✨` column. ### SSZ --- StableContainer implementation * 🐼
Last changed by  
 
Tim Beiko
626

Read more

Ethereum Forschungsingenieurtagung RSVP

The Ethereum Foundation is organizing an in-person L1 research and engineering workshop in Berlin on June 9-13, 2025. The event's aim is to advance the hardening of Fusaka implementations and make progress on a set of important topics such as EL & CL scaling, censorship resistance, the future of the EVM, staking endgames, account abstraction, and more. Expect this to be a mix between past interop events and R&D workshops. Please RSVP (once per team) by March 30 [here](ADD LINK). We'll follow up with a more detailed schedule and pre-reads as we get closer to the event. If you have any questions, please reach out to Tim Beiko or Alex Stokes.

3/20/2025
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: Pectra: all-client-pairs devnet running smoothly

5/21/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
Read more from Tim Beiko
Published on HackMD