OpenBrush 8-9, 11 milestone delivery
Hey Polkadot & Kusama community!
We are happy to deliver our work on the proposal approved on the 23rd of March 2023 and are requesting a second allocation of funds for the development of 8-9, 11 milestones of OpenBrush.
Context of delivery
The purpose of this proposal is to grow the emerging WASM smart contracts field by developing the core infrastructure product OpenBrush. As Gavin mentioned in this CoinDesk article, WebAssembly is the future of smart contracts. Also, as mentioned in the approved WASM smart contracts bounty, smart contracts parachains lead the ecosystem in terms of market adoption. However, despite WASM tech having a lot to offer, it's not being widely used now simply because of the lack of proper tooling and ecosystem infrastructure products.
OpenBrush is a core infrastructure product, a starting point, and a base for every ink! dApp. Nineteen production-grade teams and three parachains currently use OpenBrush. This proposal is the delivery of the previously approved development of the successful product, proposing the most developer-needed features validated by market feedback.
Please note that we did additional research and have made the decision not to proceed with the planned and approved 12th milestone and are not requesting funding for it. However, we were forced to do some additional scope of work in order to fix unexpected issues after the Rust nightly toolchain's latest release. More details can be found in the delivery report.
Delivery
You can find our delivery report here:
https://docs.google.com/document/d/1ff0CKjIFr_Rr4jkAuiZhVoWvmjc5MU3MyxmaIclsc4E/edit?usp=sharing
The amount was calculated as follows: The remaining amount without the last milestone is $235200/2 - $67200 = $50400. Including the costs of out-of-scope work, the amount is $50400 + $10320 = $60720. 60720/19.489=3115.60367387
Comments (8)
Requested
Proposal Failed
3
of 3Summary
0%
Aye
0%
Nay
Aye (110)0.0 DOT
Support0.0 DOT
Nay (245)0.0 DOT
This is my first comment, so please forgive me if I am being to direct, but it seems like you decided not to move forward with previously published milestones (12) and instead now ask for reimbursement for "out-of-scope" work? Presumably work that was never voted on or accepted by another referendum?
Hey @VALIDANDUM.IO , as described in the report — yes, we decided not to move forward with 12th milestone. Talking about out-of-scope work — it was not included in initial proposal and it could not be considered as some "new milestone" that we decided to replace with the initial one, but that was work that was needed to be done to achieve the delivery. As described in the report, the biggest change was making OpenBrush work on stable Rust toolchain, which was caused by changes in new versions of Rust's nightly toolchain, that was not expected to occur on the date of acceptance of previously published proposal. That took us a lot of hours to fix that, but without this we couldn't be able to deliver all the other milestones.