vspd migration coordination #231
Description
Update 2022-06-23: Things have changed, dcrstakepool is no longer functional and the majority has migrated to vspd. Some of the tasks below may no longer be necessary, while some are still nice to have. To be clear, most of them have never blocked the migration but rather suggested how to make it smoother for operators and users. See this comment for a more recent status.
- Notify operators privately
- Pick better terms to disambiguate old and new VSP staking
- A name for the new VSP staking process dcrdocs#1156
- Likely obsolete. May be no longer relevant if we have no more VSP2 tickets (until we get some VSP4 tickets :) )
-
dcrstakepoolupdates- Deprecation notice in the README (Deprecation notice. dcrstakepool#634)
- Add deprecation notice and link vspd replacement to legacy UI home page (Add deprecation notice and vspd link to UI home page dcrstakepool#635)
- Canceled. There is a PR but it was not merged (Add closing notice to homepage UI dcrstakepool#638)
-
vspdupdates- Add link to legacy dcrstakepool instance (Add link to legacy dcrstakepool instance #224)
- Canceled. There is a PR but it's no longer needed now that the legacy is gone (Support link to legacy vsp #325)
- Add link to legacy dcrstakepool instance (Add link to legacy dcrstakepool instance #224)
- dcrdocs updates
- Migration entry point for operators.
- Likely obsolete. degeri's guide posted in (VSP shutdown guidelines dcrdocs#1139) covered how to shutdown dcrstakepool. I guess the remaining step of "migration for operators" is to launch a vspd, so perhaps such an entry point is no longer needed. There was no process to carry over VSP2 tickets into a VSP3 server.
- Operating a VSP page was updated.
- VSP shutdown guidelines
- VSP shutdown guidelines dcrdocs#1139
- Still relevant for vspd and would be nice to have in a well-known place. Perhaps degeri's guide for shutting down a dcrstakepool could be ported for vspd.
- Migration entry points for users (dcrwallet, Decrediton).
- Likely obsolete. I thought it would be nice to have one link covering all aspects of migrating tickets to vspd (e.g. I had to get through some pains with CLI). I guess Decrediton users were guided by its GUI, and in any case there is no longer a choice to stay on dcrstakepool.
- Update How to Stake page
- Still talks about legacy stuff, update needed (Update How to Stake for vspd dcrdocs#1157)
- Update How to Vote
- I think its first image is still from the legacy web UI
- Update Verifying Votes
- Likely unneeded. I don't see anything specific to VSP, but someone double checking wouldn't hurt.
- Migration entry point for operators.
- Check Decrediton migration UX
- Needs to have noticeable UI clues to prompt people to migrate, e.g. warn user when buying tickets with legacy VSP.
- Done. Afaik it was implemented.
- Help users choose which vspd to use now that they are not routed through VSP's website where they can learn about the advantages of that VSP (e.g. voted/revoked stats, count of voting wallets, operator name, etc.).
- Possibly done. Does Decrediton show any info for the vspd server that helps to make a choice?
- Needs to have noticeable UI clues to prompt people to migrate, e.g. warn user when buying tickets with legacy VSP.
- decred.org updates
- list vspd instances at /vsp (Add vspd operators to /vsp dcrweb#920)
- A dashboard to track migration progress
- Ideally with charts
- Maybe something similar to voting.decred.org?
- Candidate locations: decred.org/vsp, dcrdata, PD Analytics
- Obsolete. Nothing to track now. It may be interesting to researchers to analyze how various VSPs have performed but it is out of scope of this issue now.
- VSP operators should prompt their users to migrate to their vspds via email/Twitter/etc.
- Done. I assume they did what they could.
Discussions:
- 2020-12-09: "Upcoming Changes in 1.6 for Proof-of-Stake using VSPs" has some user-friendly text about why users and operators should upgrade to vspd