# 1/24 4844-devnet breakout [Edelweiss Devnet Status Docs](https://docs.google.com/document/d/1LM7mtkWt2VcDYFtXuFVpKPt0Zh6GhZmFEv5LStUfAZQ/edit#heading=h.wyp1eafmezmr) ## Overview - Started with geth (CB prototype), prysm, lighthouse, lodestar - If you want to be a validator, let Mofi know - Teku would like to join - Genesis start @ Merge - [blob-utils](https://github.com/Inphi/blob-utils), tooling to interact with blobs - Load testing not in scope for this devnetL: given the chain is quite small, won't get much valuable data out of it - Do we plan to have an L2 deploy to a future devnet? - Coinbase is working on an implementation of OP Bedrock Stack that can do this, only need a working devnet ASAP - Was a relatively small change, but should check with other L2s once we have a stable devnet - Have you tested charging at both Genesis & Merge? - Yes, it's working. [Interop repo](https://github.com/Inphi/eip4844-interop) is setup to do that. - Data availability window: for devnet-4, it's set to 2 weeks. Should test with a shorter time. - Will there be other devnets by EOW? Yes.
Last changed by  
 
Tim Beiko
378

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
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