OpenBrush Third Grant(follow up 2)

[TtomaS7]

Preview

Project Abstract

Overview

The mission of this project is to make ink! usable and facilitate WASM ecosystem adoption.

To be successful with this mission, we have outlined several steps that would need to be taken.

1. OpenBrush is a library for secure smart contract development on ink!, same as
   OpenZeppelin on Ethereum.
2. OpenBrush should serve as a starting point for every developer entering a Polkadot(ink!) ecosystem.
3. In addition to having a standard implementation, Openbrush should also have macroses to simplify and abstract up applications(smart contracts) development.
4. For Openbrush to fulfill its purpose, several changes must be made & several blockers to be overcome in ink! and in Substrate's pallet-contracts. We are committed to doing that in the context of this project.

This project is important to us as it's our strategic goal to accelerate Polkadot ecosystem development. Applications on Ink! are a considerable part of it.

It is an application for a follow-up 2 grant. The initial grant covered the first and second milestones:

• Openbrush Milestone 1 delivery report
• Openbrush Milestone 2 delivery report

The second grant covered the 3-5 milestones:

• Openbrush Milestone 3 delivery report
• Openbrush Milestone 4 delivery report
• Openbrush Milestone 5 delivery report - It is in progress right now it depends on the ink! team, so we started work on the next milestone in paralel.

For which grant level are you applying?

• Level 3: Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

• The application template has been copied, renamed ( project_name.md) and updated.
• A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
• I have read and acknowledged the terms and conditions.
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted.

How Did You Hear About our grants program?

• Personal Recommendation
• Substrate Builders Program
• Other: Supercolony applied for the two Grants before

[semuelle]

Hi @TtomaS7, thank you for your application. Good to see SuperColony being busy. We will take a look at your application as soon as possible, we just have a bit of a backlog currently, so it might take a few days.

[TtomaS7]

Thanks!
I`m waiting for your review.

[semuelle]

Sorry for the wait, @TtomaS7. I just check your application, and it generally looks good. The only issue I have, for now, is that the total FTE for milestones 6-9, according to my calculations, is 2.63, not 3. Can you verify?

[athei]

cc @cmichi @ascjones @HCastano

[xgreenx]

Sorry for the wait, @TtomaS7. I just check your application, and it generally looks good. The only issue I have, for now, is that the total FTE for milestones 6-9, according to my calculations, is 2.63, not 3. Can you verify?

Yea, we didn't know that value we need to use. Average of 4 milestones = 2.63 or maximum among all milestones = 3. We selected maximum=)

[athei]

I see that you are planning multiple chain extensions. I think we need a way to compose them at the substrate and ink! level. Otherwise it would be quite bothersome so support more than one of them in one chain.

[athei]

Aren't those steps already done?

[xgreenx]

Yes, it was done.

We created milestones 6-8 several months ago, and we've started work on the 6th milestone before publishing the Grant for it.
We couldn't post it because the 4th milestone was not finished(we waited for the finalization of the PSPs). We've started work on the 5th milestone, but it depends on ink! team and we waited for feedback. At the same time, we started to participate in the Substrate Builders Program, where we represented milestones 6-8. We agreed that the Supercolony would not take money for the SBP, and we can apply with the same milestones for the Grant.

So we started work on it when:

• The milestone four was almost done we only waited for the finalization of PSPs.
• Part of milestone five was done, but it required feedback from ink! team.
• Milestone six is part of the SBP, but funds from the Grant that is not published.

We discussed this with the SBP team and they said that it is okay if a small part of the tasks will be ready in the grant.

We planned to publish it soon, but after:

• We got more feedback and changed the PSP, it took more time for finalization.
• We changed the scope of milestone 5 because refactoring of the storage is more critical and also affects part of milestone 6(it was not clear what the scope is).

All that created delays to post the Grant 3. And it is why part of the tasks already are ready=)

[xgreenx]

I see that you are planning multiple chain extensions. I think we need a way to compose them at the substrate and ink! level. Otherwise it would be quite bothersome so support more than one of them in one chain.

Yea, we had the same thoughts. Right now ink! supports only one ChainExtension on the codegen level. It is why we created it manually without codegen. But we have some ideas on how we can improve it and we plan to discuss it in the issue in ink! repository=)

On substrate-level we planned to use a simple model like:

match func_id {
      // Instead of 0x1 it will be actual selectors of methods. It is only for example here.
      0x1 | 0x2 | 0x3 ... | 0xF => PalletAssetExtension::process(func_id),
      0x11 | 0x12 | 0x13 ... | 0x1F => PalletUniquiesExtension::process(func_id),
      0x21 | 0x22 | 0x23 ... | 0x2F => SomePalletExtension::process(func_id),
}

If someone wants to add support for another extension, it is a separate block in match. But we can think how to better do that.

[Noc2]

Thanks for the application. I have just one question. The price per dev per week has almost doubled compared to your previous applications. Why is this the case and would you be willing to reduce the price?

[Noc2]

And keep in mind it’s usually easier/faster to get the grant accepted, in case we don’t need the additional approval from the web3 council (below 100k).

[TtomaS7]

Thanks for the application. I have just one question. The price per dev per week has almost doubled compared to your previous applications. Why is this the case and would you be willing to reduce the price?

Hello!
The price per hour was approximately 50$ in previous grant/milestones.

Formula per hour rate = Milestone Price / weeks / 5 days per week / 8 hours per day / people assigned

Milestone 1: 10000/2/5/8/2.5 = 50
Milestone 2: 35000/7/5/8/2.5 = 50
Milestone 3: 12000/4/5/8/1.5 = 50
Milestone 4: 22500/4.5/5/8/2.5 = 50
Milestone 5: 15000/4/5/8/2 = 47

We assigned more senior people for OpenBrush (the experience has been showed us that we underestimated our work) and I as Product Owner started to work on OpenBrush a lot from Marketing and promotion side - we have mentioned it on our Proposal. This is why the rate was increased to 75$ per hour.

Milestone 6: 54000/6/5/8/3 = 75
Milestone 7: 52500/7/5/8/2.5 = 75
Milestone 8: 45000/6/5/8/2.5 = 75
Milestone 9: 30000/4/5/8/2.5 = 75

And keep in mind it’s usually easier/faster to get the grant accepted, in case we don’t need the additional approval from the web3 council (below 100k).

We definitely understand that. We could split it into 6-7 and 8-9, but we don't want to create again a situation where we started working on the following Grant when we didn't deliver the previous one. We decided to make a big one for the next six months to avoid that.

[Noc2]

Thanks for the additional information and fast reply. A 50% increase is quite a lot. Could you reduce the price a little bit? My personal suggestion would also be to initially apply for milestone 6 and 7 via grants for less than 100k. But that’s up to you.

[Noc2]

Btw. it seems “set_code_hash” is already implemented use-ink/ink#1203 Is willser part of your team and could you comment on this? Also are their other parts that are already implemented?

[TtomaS7]

Thanks for the additional information and fast reply. A 50% increase is quite a lot. Could you reduce the price a little bit?

The developers' salary on the market grows, and based on the previous milestones, we always underestimate the expenses. Both influenced the rate per hour.

My personal suggestion would also be to initially apply for milestone 6 and 7 via grants for less than 100k. But that’s up to you.

Can we apply for Grant 4 with milestones 8 and 9 after the delivery of milestone 6?

[TtomaS7]

Btw. it seems “set_code_hash” is already implemented use-ink/ink#1203 Is willser part of your team and could you comment on this? Also are their other parts that are already implemented?

willser is not part of the team. Someone implemented the set_code_hash before us=)

As mentioned in that comment:

• 0. Blocked until Storage rework use-ink/ink#1217
• 1. Fully implemented by our team: seal_delegate_call api function (support for library contracts)  paritytech/substrate#10617
• 2. Fully implemented by our team: Upgradable contracts using set_code function paritytech/substrate#10690
• 3. delegate_call and Proxy example implemented by our team: CallBuilder delegated calls API use-ink/ink#1133. set_code_hash implemented not by a member of the team, related work hours are excluded from the Grant.
• 4. Done, but requires refactoring after Storage rework use-ink/ink#1217
• 5. Blocked until Storage rework use-ink/ink#1217
• 6. Done, but requires full refactoring after Storage rework use-ink/ink#1217
• 7. In progress
• 8. In progress

We didn't exclude set_code_hash from point 3 because we want the exact description of milestone six as in SBP.

[Noc2]

Thanks for the detailed reply. In this case, please remove set_code_hash and any related amount of work. Otherwise we would essentially pay you for work done by somebody else. For me it would be fine if you already apply for the next grant after the delivery of milestone 6.

[xgreenx]

Thanks for the detailed reply. In this case, please remove set_code_hash and any related amount of work. Otherwise we would essentially pay you for work done by somebody else. For me it would be fine if you already apply for the next grant after the delivery of milestone 6.

We split the grant into 6-7 and 8-9 milestones and reduced the rate to fit the < 100 000 requirement.
Removed the set_code_hash from 6.3.

[Noc2]

Thanks for the update. I’m happy to go ahead with it.

[TtomaS7]

So do we need Web3F council members on our pitch call, then?

[semuelle]

So do we need Web3F council members on our pitch call, then?

The pitch call is with the grants committee. The council reviews the application separately.

[semuelle]

LGTM. Just one request: we fund documentation of projects (articles, docs, videos, etc.), but we specifically don't fund marketing. I'd suggest removing the SEO deliverable and renaming/rephrasing the other "Marketing" deliverables.

[TtomaS7]

The pitch call is with the grants committee. The council reviews the application separately.

Good, so we don’t need all the participants on our pitch call.

LGTM. Just one request: we fund documentation of projects (articles, docs, videos, etc.), but we specifically don't fund marketing. I'd suggest removing the SEO deliverable and renaming/rephrasing the other "Marketing" deliverables.

Okay, I've removed SEO optimization part

[hakan-w3f]

Looks good to me.

[github-actions]

Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions.

Before you start, take a moment to read through our announcement guidelines for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at grantsPR@web3.foundation and we'll be happy to collaborate on an announcement about the work you’re doing.

Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀