Skip to content
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

Include option for arbitrary accounts as a reward destination #3642

Closed
jack-kearney opened this issue Sep 9, 2020 · 6 comments
Closed

Include option for arbitrary accounts as a reward destination #3642

jack-kearney opened this issue Sep 9, 2020 · 6 comments

Comments

@jack-kearney
Copy link

I noticed recently that Substrate now allows staking rewards to be redeemed to arbitrary accounts. However, it looks like this feature hasn't yet been rolled out into polkadot.js.org/apps.

If I understand the logic correctly, seems like this is the only place that would need to be updated.

Is there something else preventing this? If not, I can submit a PR to introduce the new value

@jacogr
Copy link
Member

jacogr commented Sep 9, 2020

Logged as #3354 so closing this as duplicate.

It needs detection for the different networks since not all support it, which is the only tricky bit. So the adjusted constants should only apply to networks where this is available, as detected.

@jacogr jacogr closed this as completed Sep 9, 2020
@jack-kearney
Copy link
Author

Gotcha - makes sense!

@jacogr
Copy link
Member

jacogr commented Sep 9, 2020

So did add support for at least displaying it in the account action page today (and changing when already set). But as of this moment, the best way to set it via the Extrinsics app. Once set though, can be managed via account actions.

Still have no idea how to detect the chains - can hardcode it based on genesisHash, but that is a horrible maintenance overhead tracking all of them. (I guess only Polkadot/Kusama is really important, so can just do it for those 2, i.e. Polkadot will go up on the next upgrade)

... erm, that last comment was horrible, I didn't mean anything else is not important, just that most apps users use those 2.

@jacogr
Copy link
Member

jacogr commented Sep 15, 2020

@jack-kearney Just FYI, enabled it today globally since it went live on Polkadot (and it already available on Kusama). So will create slight issues with older chains where not available... Not a perfect solution, but can set it anywhere now.

@jack-kearney
Copy link
Author

@jacogr Thanks! Super helpful to have in there. No clean solution for detecting the chain is jumping out at me. Will think on this though

@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Jun 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants