Pectra System Contracts Bytecode Audit RFP
The Ethereum Foundation is seeking proposals for a bytecode audit of three smart contracts associated with the Pectra hard fork (EIPs 2935, 7002, 7251). The audit must focus exclusively on validating the bytecode against EIP specifications and identifying security vulnerabilities, with optional suggestions for fixes. Applicants should submit a proposal via email to rfp@ethereum.org by October 11, 2024, including a work summary, timeline, and price. Accepted proposals will be confirmed by October 22, 2024.
Eligibility: Open to any qualified auditor or team capable of performing a smart contract bytecode audit; proposals must include work summary, timeline, and price.
Pipeline
Funder track record · does Ethereum Foundation actually pay grants?
🟡 Some payout evidence · 2 grantees found · last payout 2025-05-09 · checked 2026-10-31 · 0 forum reports, 7 web pages read, 1 unverifiable claims dropped
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
| Grantee | Amount | Date | Evidence |
|---|---|---|---|
| ETHPrague | — | 2025-05-09 page date | “Recipients included educational content creators, conference organizers, bootcamps and hackathons such as ETHPrague and ETHiopia.” source |
| ETHiopia | — | 2025-05-09 page date | “Recipients included educational content creators, conference organizers, bootcamps and hackathons such as ETHPrague and ETHiopia.” source |
Trust breakdown (3/3 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| deadline | 0.35 | 100% | quoted in source |
| apply link | 0.075 | 100% | link in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 100% | official page or repo |
| model confidence | 0.1 | 95% | model self-report |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 10% | model rated 10% |
| ecosystem overlap | 0.25 | 0% | ethereum vs aleo |
| category overlap | 0.15 | 17% | security, research vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 0% | solidity, geas vs rust, leo, zk |
Sources (1)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Pectra System Contracts Bytecode Audit RFP | Ethereum Foundation ESP: open RFPs (GitHub) | 2026-09-28 |
History (1)
| v | Changed | Fields |
|---|---|---|
| 1 | 2026-09-28 | created |
Extracted text
# Pectra System Contracts Bytecode Audit RFP The Ethereum Foundation is soliciting proposals for an audit of the bytecode of three smart contracts related to the Pectra hard fork. These are system contracts to be used by EIPs 2935, 7002, 7251 (linked below). They will be deployed prior to the hard fork or as part of its migration. ## Audit Requirements The audit should focus **exclusively** on the smart contract bytecode, referenced in the EIPs below. It **should not** encompass all of the EIPs, or client implementations of the EIPs, including their interactions with the contracts. The audit should validate whether the contracts' bytecode meet the functionality described in the EIPs. The audit should also highlight any potential security vulnerabilities associated with the contract, both as part of its normal utilization and by malicious users. If and where applicable, the audit should ideally propose fixes or improvements to the contract code. There is a possibility the EIP authors may make changes to the contract code after the publication of this RFP, although we do not expect their semantics to change significantly. The latest versions of the bytecode will be shared with auditors prior to the beginning of the audit. ### [EIP-2935: Serve historical block hashes from state](https://eips.ethereum.org/EIPS/eip-2935) The contract contains a ring buffer of historical block hashes and two code paths, `get` and `set`, depending on the caller. Expected calldata formats and behavior for each are specified in the EIP. ### [EIP-7002: Execution layer triggerable withdrawals](https://eips.ethereum.org/EIPS/eip-7002) The contract contains a queue of staking withdrawal requests and three code paths depending on the caller and input: `add_withdrawal_request`, `get_excess_withdrawal_requests`, and `read_withdrawal_requests`. Excess withdrawal requests beyond what the consensus layer can process are queued and a fee is calculated to prevent spam requests. In addition to the semantics in the EIP, the audit should evaluate the contract behavior prior to the first system call -- noting the initial withdrawal request fee. The first system call will occur in the first block following the hard fork, but the contract can be called before then. A [geas](https://github.com/fjl/geas) implementation of the contract can be found in [this repository](https://github.com/lightclient/sys-asm). ### [EIP-7251: Increase the MAX_EFFECTIVE_BALANCE](https://eips.ethereum.org/EIPS/eip-7251) The contract contains a queue of requests to consolidate validators in response to a consensus layer parameter change. It contains three code paths depending on the caller and input: `add_consolidation_request`, `get_excess_consolidation_requests`, and `process_consolidation_requests`. A fee is charged for consolidation requests based on excess requests to be processed, similar to 7002. In addition to the semantics in the EIP, the audit should evaluate the contract behavior prior to the first system call -- noting the consolidation request fee calculated using `EXCESS_INHIBITOR`. A [geas](https://github.com/fjl/geas) implementation of the contract can be found in [this repository](https://github.com/lightclient/sys-asm). ## Proposal Submission To submit a bid for the audit, please email your proposal to rfp@ethereum.org with the subject line "Pectra System Contracts Bytecode Audit" by October 11, 2024. 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. Accepted proposals will be confirmed by October 22, 2024 at the latest.