-
Notifications
You must be signed in to change notification settings - Fork 329
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch '@anchpop/nns-owns-dapp-canisters-for-longer' into 'master'
feat(sns): NNS1-3116: NNS root co-controls dapp canisters until the swap is finished # How to read this MR The first commit modifies NNS root to not ever hand sole control of the dapp canisters over to SNS root. Instead, NNS root adds SNS Root as a controller but also leaves itself as a co-controller. The second commit modifies SNS Swap to make SNS root the sole controller after a successful swap. # Description !19430 will disallow dangerous proposals from being submitted until the swap is done. One of these dangerous proposals is upgrading SNS-controlled canisters. But there may be an issue where an SNS-controlled canister requires an emergency upgrade during a swap. If NNS root is a co-controller, the canister will still be upgradable through an NNS proposal during an emergency. NNS root is removed as a co-controller after the swap is done, leaving only SNS root. Once this MR is merged, NNS root should not be upgraded without also upgrading SNS Swap, although nothing that terrible would happen if it were. (The consequence would be that NNS Root would remain a co-controller after the swap was done, as the new version of Swap is responsible for removing it. This would be a recoverable issue though, as all we would have to do is upgrade Swap via an NNS proposal and then call finalize.) Closes NNS1-3116 Closes NNS1-3116 See merge request dfinity-lab/public/ic!19527
- Loading branch information
Showing
12 changed files
with
200 additions
and
59 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.