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

Allow user and admin to change Decred address #472

Open
xaur opened this issue Aug 12, 2019 · 4 comments
Open

Allow user and admin to change Decred address #472

xaur opened this issue Aug 12, 2019 · 4 comments

Comments

@xaur
Copy link

xaur commented Aug 12, 2019

Afaik it is currently not easy to change the Decred address (I think it's called "voting address"?) because it requires directly editing the database.

Changing address is a legit use case if the user migrates to a new seed or just desires to rotate the address for privacy reasons.

Currently to change the address the user is advised to create a new VSP account, which is pita because it needs a new email address.

It would be nice if the user could change the DCR address himself to remove the load from the admin and also eliminate the roundtrip.

I guess admins might also need an ability to change the DCR address for the user in some circumstances.

Originally discussed in #426.

@UferePease
Copy link
Contributor

After changing the ticket address, will there be any need to use the previous ticket address again? Should the old address be kept or discarded?

@xaur
Copy link
Author

xaur commented Sep 19, 2019

The old address need to be rememberd for two reasons. One is to allow the VSP to vote for the user until all tickets from that address are voted. Another is to present historical data on past tickets.

@raedah
Copy link

raedah commented Sep 24, 2019

Recommended to close. This will be made redundant by planned privacy work.

@xaur
Copy link
Author

xaur commented Oct 3, 2019

@raedah generally agreed, question is how far away is the deployment? If it's a few months away I agree there's no need to spend effort on this. If it's e.g. 1 year away then this feature could make some use until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants