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

Multisig wrapper #116

Closed
wants to merge 5 commits into from
Closed

Multisig wrapper #116

wants to merge 5 commits into from

Conversation

RodrigoAD
Copy link
Member

No description provided.

@RodrigoAD
Copy link
Member Author

@reductionista Opened the PR with the current working branch. Please rebase it with latest develop

call() now calls prepareCall(), which creates and signs the
tx, followed by broadcast()
Similarly:
deploy() calls prepareDeploy(), then broadcasts
upload() calls prepareUpload(), then broadcasts
Also: fix compiler errors, workaround for gauntlet-core bug in
type declaration for findPolymorphic
}
}

type ICommandConstructor = (flags: any, args: string[]) => void
Copy link
Member Author

Choose a reason for hiding this comment

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

Why this "polymorphic" command? Why do we need it? We are already wrapping the commands into a multisig command

}
}

// This is a temporary workaround for a bug in the type specification for findPolymorphic in @gauntlet-core.
Copy link
Member Author

Choose a reason for hiding this comment

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

Polymorphic is a legacy command that gauntlet-core had to support for old Gauntlet EVM, but we won't be using it in the future

// For now, propose, vote, and execute functionality are all combined into one CONTRACT:COMMAND::multisig meta-command
// This is parallel to how things are implemented in Solana. The execute happens automatically as soon as the last
// vote required to exceeed the threshold is cast. And the difference between propose and vote is distinguished by
// whether the --proposal=PROPOSAL_HASH flag is passed. Later, we may want to split this into CONTRACT::COMMAND::propose,
Copy link
Member Author

Choose a reason for hiding this comment

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

We want to stick to the same process as EVM and Solana, where the multisig command tells us which step we are based on the proposal state

@RodrigoAD
Copy link
Member Author

Closing in favor of: #111

@RodrigoAD RodrigoAD closed this Feb 17, 2022
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

Successfully merging this pull request may close these issues.

2 participants