-
Notifications
You must be signed in to change notification settings - Fork 32
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
Adjust RewardDestination with entry 3 (payouts to any account) #22
Comments
Can this be bumped up the priority list? It has been an issue for a long time now. |
Yep, same problem here. Any news? Just need to change one digit, lads. |
Can we please fix this ASAP. I am stuck in a very weird spot because of this and relying on Ledger... |
If you are stuck, you can set controller to a non-ledger address using
setController() extrinsic, change the destination, then set it back to the
ledger.
…On Thu, Nov 4, 2021 at 2:58 PM Bogdan Alexandrescu ***@***.***> wrote:
Can we please fix this ASAP. I am stuck in a very weird spot because of
this and relying on Ledger...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAWXC7DKEATFWYNGHYBURTUKMF2VANCNFSM4R2XZNMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Right. @nicolasochem 's fix might work out for you. Set a controller account on Polkadot JS for your ledger account and then use it to sign the transaction for changing rewards destination address If you are new to the controller/stash account terminology, watch this video from 6.14 - https://www.youtube.com/watch?v=FCXC0CDhyS4 |
Is there a guide on how to use setController() extrinsic? How would I do this? Can this be done via the Polkadot.js extension or webapp? |
You are a genius! That totally fixed my issues! Many thanks!! |
@ainhoa-a can we re-open this issue? The root cause of the bug has not been fixed yet. |
@zaibon our latest upgrade solves this issue |
you mean v12.9200.0 ? Cause I did upgrade my ledger yesterday and still had the issue. |
Hi @zaibon the PR is still open on Ledger's side LedgerHQ#22 but should be merged soon. |
Reported here polkadot-js/apps#3770 (comment)
(It affects both apps, only logging it here since I would assume the change would be the same)
The text was updated successfully, but these errors were encountered: