-
Notifications
You must be signed in to change notification settings - Fork 66
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
Polkadot and Kusama nominator controller accounts are being deprecated #1350
Comments
8th June 2023 UpdateWestend now reflects the changes of
|
Hi @rossbulat, Many thanks for your notice, we are working on this update and will roll out the necessary changes soon. Have a good day. |
Awesome, looking forward to see the updates live :) |
Polkadot and Kusama nominator controller accounts are being deprecated
This is an issue to notify the maintainers of this repo that nominator controller accounts are being deprecated on Polkadot and Kusama, in favour of proxy accounts. In an upcoming runtime upgrade (version and date is yet to be determined), 2 call signatures of the staking pallet will change. These are breaking changes for UIs, so UIs will need to update their codebases when the changes come into effect.
Call Changes
The
staking.bond
andstaking.setController
call signatures have now changed in the Substrate codebase PR here, and will take effect in a future runtime upgrade.set_controller(controller)
will becomeset_controller()
. This call will simply set the controller account to the caller's stash account, if it is not already.bond(controller, value, payee)
will becomebond(value, payee)
. This call will now set the caller as the controller account (same as the stash).UIs can prepare now by adding a controller deprecation message, and allow stakers to change their controller accounts back to their stash using the existing
staking.setController(controller)
call. The Polkadot staking dashboard recently deployed this functionality and may be useful as reference code.Next Steps
Other Resources
The text was updated successfully, but these errors were encountered: