A potential pattern to use multisig owned objects#5
Draft
nikos-terzo wants to merge 7 commits intomainfrom
Draft
A potential pattern to use multisig owned objects#5nikos-terzo wants to merge 7 commits intomainfrom
nikos-terzo wants to merge 7 commits intomainfrom
Conversation
Multisig address can create the SharedSpace non-transferable object which can be used to authorize specific combination of multisig members.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I explore a way of having some objects under a single multisig address, which participants can use but only if they have the correct authorization to do so.
More specifically, a SharedSpace object is signed by the participants of the multisig address and a correct MemberProof is created identifying which keys authorized the multisig transaction. This MemberProof can later be used to limit the actions that the multisig sender can do with the object under it.
In the example I have created the only_admin_transferable_mintcap package which creates a MintCap that is managed (transferred & updated) only with the AdminAuth (1st-participant) but used for minting only by the MintAuth (2nd-participant).