# 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](https://eips.ethereum.org/EIPS/eip-4788). A recent specification change, implemented in [this pull request](https://github.com/ethereum/EIPs/pull/7456), 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](https://github.com/quilt/etk) implementation of the contract can be found in this repository: https://github.com/lightclient/4788asm The audit should validate whether the contract bytecode meets the functionality described in the EIP ([see the diff](https://github.com/ethereum/EIPs/pull/7456/files#diff-8e3f79bb190496941350728d7a0254c2090bea9049db35245dbe1b206f3bcec7R82)), specifically that the `set` and `get` functions safely enabling the storage and querying of `timestamp` and beacon roots. The audit should also highlight any potential security vulnerabilities associated with the contract, both as part of its normal utilisation and by malicious users. If and where applicable, the audit should ideally propose fixes or improvements to the contract (byte)code. ## Proposal Submission To submit a bid for the audit, please email your proposal to [email protected] with the subject like "EIP-4788 Contract Bytecode Audit" by August 21, 2023. Proposals should include a summary of work to be performed, a timeline for completion of the audit, and a price for the engagement. Proposals will be judged on technical expertise, possible start dates, and cost, at the discretion of the Ethereum Foundation. Ideally, auditors could begin work on the project 1-3 weeks after the proposal is confirmed, and deliver a preliminary report within 1-2 weeks. Accepted proposals will be confirmed by August 29, 2023 at the latest.
Last changed by  
 
Tim Beiko
467

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