Feature/canonical cw3 cw4 step1 #4293
Draft
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
jstuczyn
force-pushed
the
feature/delayed-dkg-start
branch
from
e54bed6 to
169f8f2
Compare
jstuczyn
force-pushed
the
feature/canonical-cw3-cw4-step1
branch
from
86f7017 to
86d8048
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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 is a step 1 towards making us use canonical cw3-flex-multisig and cw4-group contracts. Right now I've just included make directives to build the relevant wasm blobs.
The remaining changes will need to be made in our deployment to:
However, there will be one change of the behaviour that I'm not 100% sure we want, i.e. the other group members, i.e. the DKG participants will be able to create their own proposals. But is it a problem given that even if there was a malicious proposal, we'd need a quorum to actually pass it?
For the time being I'm leaving this PR as a draft as the result of this question.
PR chain: #4288 => #4289 => #4290 => #4291 => #4292