Given the successful completion of OpenZeppelin’s security review of the ink! smart contract language & Substrate’s smart contracts pallet, this community proposal is for the second installment supporting OpenZeppelin’s work. During this engagement, OpenZeppelin identified 11 total issues within the codebase. We are pleased to report that working with the Parity team throughout this process has been fantastic.

The finalized report can be found on OpenZeppelin’s blog: https://blog.openzeppelin.com/security-review-ink-cargo-contract/

The ink! team has acknowledged all issues. Two of the ink! issues have been solved, seven of the cargo-contract suggestions have been implemented; the rest are actively being addressed.

[Full proposal here](https://docs.google.com/document/d/1GJ2MqMgAUylk0dVfxCp5-1JVd_El3EjgrWLyE3P_iw0/edit?usp=sharing)

:
1. OpenZeppelin’s security review of the ink! smart contract language & Substrate’s smart contracts pallet is successful. 
2. This community proposal is for the second installment supporting OpenZeppelin’s work. 
3. 11 issues within the codebase have been identified. 
4. Parity team and ink! team have been working collaboratively to address the issues. 
5. Two of the ink! issues have been solved, seven of the cargo-contract suggestions have been implemented. 
6. The rest of the issues are actively being addressed.

#299 ink! design security review by OpenZeppelin (treasury proposal 2/2)

No Active Proposals