OpenZeppelin is requesting proposals for a third-party security audit of OpenZeppelin Contracts. We invite auditors to submit a proposal by June 30th for consideration. We are looking for an experienced team with demonstrated success in professional smart contract auditing.
OpenZeppelin Contracts is a widely used smart contract library, offering Solidity implementations of the major standards along with a system of modular extensions and assorted utilities for smart contract development, with a focus on security, modularity, and extensibility. It is an open-source project maintained by OpenZeppelin, a company that provides an extensive range of security products and services for blockchain applications. While OpenZeppelin has its own auditing team, we are looking for an external audit to further enhance the security of the Contracts library.
OpenZeppelin Contracts has been downloaded 4 million times from npm and it has over 10K stars and over 20K open source dependent repositories on GitHub.
Previous versions of the library have been independently audited. In October 2018, version 2.0.0 was audited by LevelK. The codebase has since evolved with a large number of new contracts and features added, and some of the previously audited code was refactored.
The audit should be performed on the git commit corresponding to the latest release at the time the audit begins. At this moment, the latest release is v4.1.0.
The audit is divided in 5 separate scopes, and proposals should provide a separate quote and time estimate for each. The final engagement may consist of all or a subset of these scopes, depending on budget and time constraints.
The file paths below are relative to the
contracts directory in the repository. Note that some of these files haven’t been released yet and they are not found in the tag for v4.1.0, so you should refer to the current latest commit.
A sibling library called OpenZeppelin Upgradeable Contracts is a variant of the codebase that is automatically transformed so as to be usable with upgradeable proxy deploments. This transformation is mechanical and automated by a purpose-built Upgradeability Transpiler.
In Scope 5, we request a review of an informal specification of the syntatic transformations implemented in the Upgradeability Transpiler. The review should assess whether the transformations preserve the security of the original code, and protect against upgradeability hazards. This specification is still being written, and a preliminary version can be seen here.
It should be taken into consideration that the audited contracts will be used as modules, combining them through inheritance with other Solidity code, and possibly overriding internal functions of the library. A small set of internal functions are by design meant to be overriden (a list will be provided later). For functions outside of this set, some care is taken so that overriding them does not cause significant soundness issues, but users are warned that they should do this at their own risk.
Proposals should include at least all of the following items, which will be taken into consideration to determine which proposal is selected.
- Timeline. Proposed start date of the audit and estimated duration for each of the separate scopes. Allocated time to review changes made in response to the reported findings.
- Approach. An overview of how the audit will be approached, describing tools and techniques used (including manual review and/or automated analysis). Expected communication with the developers of the project. Format of deliverables with examples from prior audits.
- Prior Experience. Please share your team’s work history auditing Ethereum smart contact systems with past audits and references that can be contacted upon request.
- Fees. Specified separately for each of the scopes. The fees should be fixed-scope.
Send your proposal to firstname.lastname@example.org. The deadline for submission is June 30th, 2021.