Supersig

This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines! Lines starting with a > (such as this one) can be removed.

See the Grants Program Process on how to submit a proposal.

Team Name: Decentration
Payment Address: (BTC)37hhQbMnXTrEgFnQUA9xJEeQMW7DuGvxuz
Level: 2

⚠️ The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.

Project Overview 📄

"A Supersig is a Multisig with superpowers"

A new pallet that improves on the the very-well-used multisig, but making it fit for functioning more like a larger fund, sub-treasury, DAO, or as we like to call it a DOrg.

This is Decentration's first grant proposal to Web3. We view this simple, suitable and potentially pervasivaely used pallet as a great opportunity to develop an ongoing relationship with Web3 Foundation, given that we have shared and aligned interests.

These pallets improvements have already created a lot of interest and feedback from people in the community and on twitter, so we believe its a valuable use of resources.

We also believe in building things people need rather over-engineering without validation. The simplicity of this pallet is a great example of this.

Overview

a supersig is like a multisig but with superpowers.
The first version lets you add and remove members, and has simpleMajority voting for all calls.
Kabocha (parachain candidate) and Edgeware network will use this, but we believe all chains will benefit from it.
The pallet will be unit tested and benchmarked.
Our team is interested in this as we are building out "DGov" (decentralised governance) functionality for Kabocha. "Pallet Supersig" is but one of the multiple pallets we are building, which aims to benefit substrate chains. Our focus is on making Kabocha a grassroots substrate chain that benefits the wider substrate community.

Project Details

Mockups/designs of any UI components: You can also view the diagram here Or here.
An overview of the technology stack to be used: Simple substrate pallet.
Documentation of core components, protocols, architecture, etc. to be deployed: pallet_supersig Trello ticket
- - PoC/MVP or other relevant prior work or research on the topic. As a small team we have:
- launched Kabocha crowdloan
- developed pallet_mint: where funding proposals that are approved mint new coins, instead of from a treasury. https://github.com/kabocha-network/parachain/pull/6
- (upcoming) planning on-chain proposal system called "pallet_proposals" which will begin as a level 2 grant.
- maintaining a community run Rococo fork called Pop-Art
- Maintaining and upgrading Substrate Recipes for the benefit of the Substrate community.
What your project is not or will not provide or implement
- In this grant proposal we are focussing on the first minimimal viable version of the pallet, where threshold is enumerated to various options including simple and superMajority; and add/remove member functionality. We envisage many directions this can go and many features to improve it, but will stick to this simple implementation in the MVP. We also (in the second milestone) be adapting the polkadot-js-ui, as we do envisage visualising members in the Accounts and Address Book section would be very useful.
- We wont be creating a brand new UI, but this may be part of another proposal which will encompass various pallets we are working on.

Ecosystem Fit

Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions:

Where and how does your project fit into the ecosystem? It gives teams and sub-communities the opportunity to manage more funds, and add and remove members, while having a enum (simpleMajority) quorum that is not fixed x/n.
Who is your target audience?
- Multsig users of Substrate chains, who desire the extra features we have collected from feedback.
- Groups of people who want to self-bond a validator together.
What need(s) does your project meet? It helps users of Substrate chains improve the fund management of the teams and projects that get funded by the community treasury.
Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem?
- pallet_collective is very similar, but as there are only a limited number of instances available, and such instances needed a general on-chain upgrade to instantiate, it is not useful for our needs.

Team 👥

Team members

Name of team leader: Ramsey Ajram
Names of team members: Timothée Delabrouille, Nathan Gardet, Jan Kraus, Eljo Prfiti, Richard Wells

Contact

Contact Name: Ramsey Ajram
Contact Email: ramsey@decentration.org
Website: https://kabocha.network

Legal Structure

Registered Address: Digital Trust Company
Registered Legal Entity: Decentration Trust Company (470-2018-233-GB-001)

Team's experience

Ramsey (decentration) - Substrate Engineer, Product manager, startup technical founder. Leading Kabocha's chain development and launch; Designer pallet_mint (done), pallet_proposals (ongoing). Here is a recent contribution from Ramsey in a Substrate Seminar

Timothée Delabrouille (tdelabro) - Substrate / Rust Engineer, founder of Rusty Crewmates, contributor to Kabocha

Nathan Gardet-Derc (erudyx) - Substrate / Rust Engineer, contributor to Kabocha, Rusty Crewmate. developer on pallet_mint

Jan Kraus - Full stack deveveloper - Javascript / Typescript / React / Node.js / Next.js / Gatsby / Ruby on Rails

Elio Prfiti - Substrate Engineer - Kabocha - Upgraded Substrate Recipes... https://wiki.kabocha.network/recipes

Richard Wells - Decent Partners, Kabocha founding steward, key stakeholder and communicator.

Team Code Repos

Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine.

Team LinkedIn Profiles (if available)

Development Status 📖

pallet started here: https://github.com/kabocha-network/pallet_supersig/tree/polkadot-v0.9.16

Description in trello ticket: https://trello.com/c/qi4Nf2YT

*We are now working on the Supersig pallet (pallet_supersig). This pallet will benefit multisig users of Substrate based chains.

The Supersig pallet is a multisig with super powers. It allows you to add and remove members of the multisig. It extends the capabilities of a multisig so it can be fit for governance of larger funds.

A multisig transaction acts more like a treasury proposal. And the signatures become votes, with a quorum that can be changed (but in the MVP is fixed to simpleMajority).*

Development Roadmap 🔩

This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories here. Since these will be part of the agreement, it helps to describe the functionality we should expect in as much detail as possible, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected.

Below we provide an example roadmap. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We recommend that teams structure their roadmap as 1 milestone ≈ 1 month.

For each milestone,

pallet_supersig public methods

Create a supersig

create_supersig will create a supersig with specified parameters, and transfer an existencial deposit from the creator to the generated supersig account, to bring the account to life. The dispatch origin for this call must be Signed.

The threshold is currently u128, but will be Enum.

pub fn create_supersig(
   origin: OriginFor<T>,
   members: Vec<T::AccountId>,
   threshold: u128, 
  )

Submit a call to a specific supersig

submit_call will create a proposal on the supersig, that members can approve. This will lock an amount that depend on the length of the encoded call, to prevent spam. The dispatch origin for this call must be Signed, and the origin must be a supersig member.

pub fn submit_call(
   origin: OriginFor<T>,
   supersig_id: T::AccountId,
   call: Box<<T as pallet::Config>::Call>,
  )

Vote for a call in the supersig

approve_call will add a positive, unique vote to the specified call proposal. If the numbers of votes on this proposal = SimpleMajority (51%), then the call is executed. The dispatch origin for this call must be Signed, and the origin must be a supersig member.

pub fn approve_call(
   origin: OriginFor<T>,
   supersig_id: T::AccountId,
   call_index: CallIndex,
  )

Remove a call from the supersig

remove_call will remove a call from the poll. For trensparency reasons, the votes won't be removed. This will also unlock deposited funds. The dispatch origin for this call must be Signed by either the supersig or the account who submitted the call.

pub fn remove_call(
   origin: OriginFor<T>,
   supersig_id: T::AccountId,
   call_index: CallIndex,
  )

Add member to the supersig

pub fn add_member(
      origin: OriginFor<T>,
   supersig_id: T::AccountId,
   call_index: CallIndex,
  )

Remove member from the supersig

pub fn remove_member(
      origin: OriginFor<T>,
   supersig_id: T::AccountId,
   call_index: CallIndex,
  )

Milestone 1 to make a working, secure and usable pallet_supersig v0.1.0.

The pallet will be tested on the Pop-Art, community run relay test network
The pallet will be well benchmarked.
The pallet will be functioning in both Kabocha and Edgware chains at the minimum.
Unit integration tests
Easy to spin up node to test pallet
Clearly written as Readme and inline documentation

Milestone 2 will make the Supersig as visible of an experience within the polkadot js UI as Multisig, The PR will be made, and if there is a blocker, then the apps.decentration.org fork will house the feature.

Polkadot JS UI will be forked and adapted to show the Supersig IF the chain has the pallet installed.

Milestone 3 Will get feedback and make some improvements. One improvement is adding a "Super Beneficiary" option that allows a threshold of 2/n only if the Super Beneficiary is involved in the transaction. Else the transactio will default to a superMajority. This allows for greater than the usual 2/3 multisig, but without loss of security.

⚡ If any of your deliverables is based on somebody else's work, make sure you work and publish under the terms of the license of the respective project and that you highlight this fact in your milestone documentation and in the source code if applicable! Teams that submit others' work without attributing it will be immediately terminated.

Overview

Total Estimated Duration: 5 to 7 weeks
Full-Time Equivalent (FTE): 2
Total Costs: USD 27,000

Milestone 1 — pallet_supersig MVP

Estimated duration: 3 to 4 weeks
FTE: 2
Costs: 14,000 USD

Number	Deliverable	Specification
0a.	License	Apache 2.0
0b.	Documentation	We will provide inline documentation of the supersig pallet's code, and a basic tutorial that explains how a user can spin up one of our Substrate nodes and send test transactions, which will show how the supersig functionality works.
0c.	Testing Guide	Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.
0d.	Docker	We will provide a Dockerfile that can be used to test all the functionality delivered with this milestone.
0e.	Article	We will publish an article that explains supersig pallet to developers on medium and subsocial; and a substrate workshop/seminar that explains that shows how the pallet was designed (if there available slot, else a video shared on youtube).
1.	Substrate module: pallet_supersig	We will create a Substrate pallet that will allow user you to create a "supersig" where users can be added and removed. All extrinsics will require a simpleMajority to approve. The clear difference from multisig is that the supersig address is not a composite of its signatories, therefore it will stay static when adding or removing signatories.
2.	Benchmarking	The pallet will be benchmarked and unit tested using worst case weightings.

Milestone 2 — Supersig for Polkadot JS UI

Estimated duration: 2 to 4 weeks
FTE: 1.5
Costs: 7,000 USD

Number	Deliverable	Specification
0a.	License	Apache 2.0
0b.	Documentation	We will provide inline documentation and a tutorial with a polkadot-js apps fork that guides a developer to simply set up supersig pallet and UI.
0c.	Error messages	Core functions will be fully covered by very informative error messages.
0d.	Docker	We will provide a Dockerfile that can be used to test all the functionality delivered with milestone 2. The dockerfile will be a polkadot JS UI fork, it will also be the smallest possible file size (MBs not GBs)
0e.	Article	We will publish an article that explains supersig pallet to the end-user. The article will be on medium and subsocial.
1.	Substrate module: pallet_supersig	We will create a Substrate module from Milestone 1 that will be connected to a substrate chain as mentioned in 2.
2.	Substrate chain	We will create a custom substrate template that will contain pallet supersig
3.	Polkadot JS Apps UI Fork	We will add the custom feature to a polkadot JS UI fork (and make a PR to the main repo), so that the user can see the pallet in action, end to end.

Milestone 3 — Testing Feedback and Improvements

Estimated duration: 2 to 3 weeks
FTE: 2
Costs: 6,000 USD

Number	Deliverable	Specification
0a.	License	Apache 2.0
0b.	Documentation	We will update inline documentation and tutorials based on updates and feedback gained from user interviews.
0c.	Testing Guide	If required we will update unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.
0d.	Docker	We will update the Dockerfile from previous milestones.
0e.	Article	We will update our prior articles if we have made any changes during this milestone.
1.	User interviews, feedback iteration	We will conduct user interviews to collate feedback and put them in a task backlog. We will select priorities that fit within the scope of this grant, which will be updated. From the findings of our feedback, a backlog of future tasks may be added on our kanban baord to create minor/major version bumps, and would inform the priority of future work. This milestone is vague because we are using this time to finding out unknowns to make changes with care (and in Good Faith).
2.	Substrate module: pallet_supersig	We will make any necessary updates from previous milestones.
3.	Polkadot JS Apps UI: Polkadot JS UI Fork	We will make any necessary updates from previous milestones.

Future Plans

Improvements:

make it accessible in Kabocha and Edgeware after testing, then promote the pallet in the Substrate community, and invite other communities to include the pallet;
feature to change the quorum. Or have different quorums filtered by different categories (like proxy filter)
Add Option Master Beneficiary (see here)
We can envisage is making the pallet more compatible in the polkadot-js-apps UI.
We then aim to improve the functionality of the pallet based on feedback.

Additional Information ➕

Who can vouch for Ramsey(Decentration)? Josh Muir (Kusama Council and Dat Dot), Bruno Škvorc, Dan Shields, Will Chevdor, Sacha Lanski...

Project Overview 📄​

Overview​

Project Details​

Ecosystem Fit​

Team 👥​

Team members​

Contact​

Legal Structure​

Team's experience​

Team Code Repos​

Team LinkedIn Profiles (if available)​

Development Status 📖​

Development Roadmap 🔩​

pallet_supersig public methods​

Overview​

Milestone 1 — pallet_supersig MVP​

Milestone 2 — Supersig for Polkadot JS UI​

Milestone 3 — Testing Feedback and Improvements​

Future Plans​

Additional Information ➕​

Project Overview 📄

Overview

Project Details

Ecosystem Fit

Team 👥

Team members

Contact

Legal Structure

Team's experience

Team Code Repos

Team LinkedIn Profiles (if available)

Development Status 📖

Development Roadmap 🔩

pallet_supersig public methods

Overview

Milestone 1 — pallet_supersig MVP

Milestone 2 — Supersig for Polkadot JS UI

Milestone 3 — Testing Feedback and Improvements

Future Plans

Additional Information ➕