-
Notifications
You must be signed in to change notification settings - Fork 316
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
feat(nns): Implement proposal execution for updating settings for root #866
Conversation
Another thing you (can|should) mention in the "Why" section:
IOW, it should explain why root is special (the short answer is that its set of controllers is different compared to other NNS canisters). |
877724d
to
870aa72
Compare
dfinity#866) # Why The `update_canister_settings` proposal type should work on cansiters controlled by root (already implemented) as well as root itself (this PR) Only a controller of a canister can change its settings. lifeline is the controller of root. Therefore, execution of update settings proposals that target root are implemented by calling a (new) method of lifeline. Whereas, for all other NNS canisters, update settings proposals are implemented via a call to root. # What * Add an endpoint on the lifeline (update_root_settings) * Call `Lifeline::update_root_settings` from Governance for proposal execution * Minor changes * Fix the error messages for some times * Fix the lifeline.did which was out-dated
Why
The
update_canister_settings
proposal type should work on cansiters controlled by root (already implemented) as well as root itself (this PR)Only a controller of a canister can change its settings. lifeline is the controller of root. Therefore, execution of update settings proposals that target root are implemented by calling a (new) method of lifeline. Whereas, for all other NNS canisters, update settings proposals are implemented via a call to root.
What
Lifeline::update_root_settings
from Governance for proposal execution