feat: Treasury-Multisig pallet for Planck - with parity multisig #349
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
czareko
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is kept open solely to document and preserve our design ideas related to multisig and treasury integration.
As Quantus, we aim to be a direct user of multisig functionality. Using the default Parity multisig would force us to constrain our requirements and build a significantly more complex UI on top of it.
While the treasury concept proposed in this change is valid, achieving the full potential of our other features requires a custom multisig implementation.
Our current vision is described here:
https://github.com/Quantus-Network/chain/wiki/Quantus-Multisig-Pallet-Specification
Develoment of this concept will be continued here:
#feat: Custom Multisig Pallet