Skip to content

Supersig: second grant proposal to be included in system level chain (statemine)#1630

Merged
Noc2 merged 6 commits intow3f:masterfrom
decentration:supersig
Mar 27, 2023
Merged

Supersig: second grant proposal to be included in system level chain (statemine)#1630
Noc2 merged 6 commits intow3f:masterfrom
decentration:supersig

Conversation

@decentration
Copy link
Copy Markdown
Contributor

@decentration decentration commented Mar 21, 2023

Project Abstract

Supersig has completed it's first grant. This follow up grant is required to make the necessary changes in order for it to be included in Statemine, Polkadot JS main repo, and approved by the Fellowship.

Supersig is like Multisig but provides more flexibility when it comes to scaling your organisation. You have features such as:

  • you can add and remove members;
  • enumerated threshold (i.e. simpleMajority, instead of fixed threshold);
  • and you have the option to add either Standard users which is 1 vote for 1 user, or Master users which has 50% voting power,.

If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
  • 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 (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Mar 21, 2023

CLA assistant check
All committers have signed the CLA.

@Noc2 Noc2 self-assigned this Mar 21, 2023
Copy link
Copy Markdown
Contributor

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the application. I have a couple of initial questions:

  • First, did you consider applying for treasury funding with this? With our grants program, we focus more and more on teams that are unfamiliar with our ecosystem and ask teams that are familiar with the treasury to apply there for funding.
  • One thing that might be controversial regarding the application is that you plan to/have your own token KAB, see our guidelines: https://github.com/w3f/Grants-Program#guidelines
  • Regarding the deliveries, ideally, these contain as many details as possible. For example, what do you mean by “various changes,” and do you have a mock-up or UI design you can share already?

@Noc2 Noc2 added the changes requested The team needs to clarify a few things first. label Mar 21, 2023
@decentration
Copy link
Copy Markdown
Contributor Author

decentration commented Mar 21, 2023

Hi @Noc2 David, thanks for your questions.

Re: launching this with the polkadot treasury funding, i'm not sure this grant is completely suitable for the polkadot treasury, especially as it may take at least 6 weeks to get confirmation of the work. And for sure, i would also like to make a proposal to the polkadot treasury for a new project once supersig mission has been delivered into a system chain. I think for such a raw public process one needs to be ready to deal with the stresses of a public treasury, which i may be more prepared for in coming months.

Due to time, suitability and the increased stress level, we would much prefer W3F at this time if that's not an impossibility? Though for a future project it's definitely a consideration.

As I have seen various projects getting multiple second grants with W3F, this is why i saw this as a possible track. Also I have had a pleasurable experience interacting with this process, so that's something I wouldn't want to give up.

Supersig second w3f grant is a continuation of the same project, and we want to make those grant dollars as valuable as possible, so that the tools are used by the most people, we want to be part of the percentage of grants that have made a big impact.

Re: not having a token... Let me clear up. Decentration is independent of any chain, we do not have our own token, and we haven't launched a token. To clarify, we got a small grant to build Kabocha parachain on behalf of Edgeware. The KAB you are referring to is Kabocha parachain token. The KAB is not on any exchanges and didn't go through a token sale. Decentration has 1.5% of KAB and W3F has 7% of that token, and Edgeware community own 90%, but nothing was sold, it is currently still in an experimental playground phase, but even if it was an active token, we are not the object of it, we just earned some for doing the work, but the community were unable to put it on an exchange so no market cap, which was a shame for us because we earned tokens that have not much value, so that is actually why we need to find other ways to work and get funded in this ecosystem and earn to work. Personally, I am not interested in launching a token. I prefer to build universal tools and common good parachains. Let me know if that is not sufficient to clear up that issue?

Re: Details of milestone 2 UI, yes my apologies I forgot to add mockup let me add that in.

Let me know if the initial two points are not sufficient for you? and perhaps I can try clarify further.

Cheers

Copy link
Copy Markdown
Contributor Author

@decentration decentration left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mockup added and more clarity for M1 polkadot-js

@decentration
Copy link
Copy Markdown
Contributor Author

hi David @Noc2, let me know if the above is not sufficient for you? and apologies for the longish response.

Noc2
Noc2 previously approved these changes Mar 23, 2023
Copy link
Copy Markdown
Contributor

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the quick reply here. Sounds good to me. I will share it with the rest of the team.

@Noc2 Noc2 added ready for review The project is ready to be reviewed by the committee members. and removed changes requested The team needs to clarify a few things first. labels Mar 23, 2023
@decentration
Copy link
Copy Markdown
Contributor Author

Thanks @Noc2 just to confirm it says 5 approving reviewers required, let me know if that was intentional? cheers.

@Noc2
Copy link
Copy Markdown
Contributor

Noc2 commented Mar 23, 2023

This is because GitHub doesn't allow us to have different PR rules for different PRs. We will merge it after three approvals.

@keeganquigley
Copy link
Copy Markdown
Contributor

Thanks for the application @decentration it looks like an interesting update. Happy to see that Joe and Jaco gave feedback. A couple of comments:

  • Usually 0a - 0d are mandatory for every milestone. I see you replaced testing with the error messages in M2. Will you still provide unit tests and/or e2e tests for the UI in M2? If so can you add that section back in?
  • Is your custom UI meant to be easier to use than Polkadot-JS? What other advantages will it have?

@decentration
Copy link
Copy Markdown
Contributor Author

decentration commented Mar 23, 2023

hello @keeganquigley thanks for the feedback:

  1. indeed, my apologies, it will have a suitable testing guide with end to end tests, that will be seamless for the reviewer.

Is your custom UI meant to be easier to use than Polkadot-JS? What other advantages will it have?

Yes, I personally love polkadot-js and the tool suite as an engineer, however the Custom UI, will be simpler and more bespoke to organising, initially around supersig. It will begin with similar features to page-supersig on polkadot-js app, however it will be the foundation for then future building blocks, such as: multisig interface, automated payments, and other statemine/mint primitives, etc. We can prioritise on what those will be based on feedback, and in future milestone. With our own interface we have the freedom to create something different and specific to a core set of interrelated tools, rather than abide by polkadot-js which is designed to encompass basically everything.

Let me know if that is not sufficient in dealing with your questions? : )

Cheers

Copy link
Copy Markdown
Contributor

@keeganquigley keeganquigley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes @decentration happy that you want to keep working on it. Based on your team's previous reputation I'm happy to approve.

@decentration
Copy link
Copy Markdown
Contributor Author

Thank you @keeganquigley I appreciate those words.

@Noc2 Noc2 merged commit 867ba65 into w3f:master Mar 27, 2023
@github-actions
Copy link
Copy Markdown
Contributor

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! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for review The project is ready to be reviewed by the committee members.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants