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/](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)

Proposal: ink! design security review by OpenZeppelin (treasury proposal 2/2)



- OpenZeppelin successfully completed a security review of the ink!'s smart contract language & Substrate’s smart contracts pallet. 
- This proposal is for second installment in support of their work.
- OpenZeppelin identified 11 issues which have been acknowledged by the ink! team.
- Two of the ink!'s issues have been solved, seven of the `cargo-contract` suggestions have been implemented. 
- Rest of the issues are actively being addressed. 
- The finalized report can be accessed on the OpenZeppelin’s blog. 
- Full proposal is linked.

#1762 Proposal: ink! design security review by OpenZeppelin (treasury proposal 2/2)