-
Notifications
You must be signed in to change notification settings - Fork 8
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
Multisig wrapper #116
Conversation
@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
3f8b33e
to
f97ec19
Compare
1413ecb
to
f7891ab
Compare
} | ||
} | ||
|
||
type ICommandConstructor = (flags: any, args: string[]) => void |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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, |
There was a problem hiding this comment.
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
Closing in favor of: #111 |
No description provided.