-
Notifications
You must be signed in to change notification settings - Fork 50
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
Legacy dcr.farm not available #146
Comments
Following the discussion and recommendations in the Matrix Pos Ops channel, I shut down the web interface to prevent Decrediton users to buy new tickets.
Yes the wallets are still up and I do plan to keep them up until all tickets vote.
Right now it's down to 32 live tickets.
Yes my understanding is that we should shut down dcrstakepool at this point.
Please go ahead and delist it. |
Thanks for quick reply! Great status page (it reminds me how I miss charts.dcr.farm :sad_face:). Let's close this issue when #145 is merged. |
Maybe I should write up a proposal to bring it back and make it sustainable... |
#145 is now merged and the legacy dcr.farm VSP is removed from the VSP list. Closing this issue. The status page shows that one legacy wallet is still up, thanks for keeping it up. @infertux if you can share its live ticket count it would help our statistics on user migration to vspd.
Not a bad idea. Organizing a proposal takes a bunch of hours and there is no guarantee it will pass, but the most recent "non-core" dev Twitter bot proposal passing was a good signal. Another funding route is to contribute similar functionality to dcrdata (escaping to avoid linking: I'm getting off-topic to this issue but feel free to join our #services chat to discuss further. |
https://dcr.farm/api/v2/stats now redirects to https://vsp.dcr.farm/ . Last time it responded on
2021-06-11 07:25:44
and had 40 live tickets, according to the gsd endpoint. The vsp page also says it was last updated 11 days ago.In such state, I think it should be delisted and its removal is already included in #145. But I'd also like to hear from @infertux:
The text was updated successfully, but these errors were encountered: