The safety of the Ethereum protocol is frequently being improved, and one latest effort is the exterior safety evaluate of the Pectra System Contracts.
The outcomes of this evaluate might be discovered within the audits repository, and the TL;DR is that each one found points deemed related or necessary from these evaluations have been addressed.
Audit Scope and Methodology
The Pectra System Contracts embody a number of EIPs (EIP-2935, EIP-7002, and EIP-7251), and evaluations have been primarily executed to:
- Consider the contracts for potential assault vectors.
- Make sure that the contract logic precisely implements the supposed performance as per the EIP specs.
A multi-phase method was taken, with every audit constructing upon the findings of earlier ones:
- Blackthorn Audit
- Dedaub Audits
- PlainShift Audit
- Sigma Prime Audit
Between every evaluate, code enhancements have been made earlier than continuing to the subsequent spherical of audits.
Formal Verification
Along with the safety evaluations listed above, a16z performed a Formal Verification using Halmos.
They used Halmos to formally confirm the purposeful correctness of those contracts. This particularly targeted on whether or not the bytecode aligned with the spec, somewhat than evaluating the safety of the spec itself towards potential abuse or malicious use. This separation of issues permits auditors and the group to evaluate the spec with out worrying about low-level bytecode implementation particulars.
Subsequent Steps
The total experiences might be discovered within the Pectra System Contracts Audits repository.
A bug bounty competitors is at the moment working on Cantina has rewards of as much as $2,000,000 for findings associated to Pectra.
As all the time, the safety of the Ethereum ecosystem is a collective effort. We prolong our gratitude to all of the auditors and contributors who’ve performed an necessary half on this course of!
