Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Contract Deployments & Interactions with a Multisig #475

Open
wottpal opened this issue May 5, 2023 · 2 comments
Open

Support Contract Deployments & Interactions with a Multisig #475

wottpal opened this issue May 5, 2023 · 2 comments

Comments

@wottpal
Copy link

wottpal commented May 5, 2023

No description provided.

@statictype
Copy link
Contributor

what do you mean?

@wottpal
Copy link
Author

wottpal commented May 6, 2023

Of course, sorry I should have done this in the first place: Professionally deployed smart contracts that have admin- or upgrade capabilities should not be governed or deployed by a single wallet, but instead a multisig account. Doing so is right now only supported by either using polkadot.js/apps or custom scripting as far as I know.

The process looks like the following:

  1. You initiate the deployment transaction on one machine (probably by passing a special flag/function to indicate that it's an "unfinished" multisig transaction.
  2. Copy over the call-data hash to all necessary signatory machines and continue/finish the transaction there.

Would be nice to make this possible within contracts-ui as well.

@wottpal wottpal changed the title Support Contract Deployments with a Multisig Support Contract Deployments & Interactions with a Multisig Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants