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)

Democracy

Propose and approve a spend of treasury funds.

- `origin`: Must be `SpendOrigin` with the `Success` value being at least `amount`.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.

:
1. OpenZeppelin completed a security review of the ink! smart contract language & Substrate's smart contracts pallet
2. Found 11 total issues 
3. Parity team worked great throughout the process
4. Two of the issues have been solved, seven are implemented, rest are actively being addressed

Requested: 0.25 undefined

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