-
Notifications
You must be signed in to change notification settings - Fork 74
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
getstakeinfo/stakepooluserinfo use is problematic due to addticket usage #180
Comments
The goal is to keep migrating functionality over to stakepoold. I think stakepooluserinfo can eventually be removed. Rough TODO would be:
|
Item 3 is in progress now too. 2 and 4 may have to be split out and planned for the next release cycle. There are a lot of dcrwallet/stakepoold changes in-flight already. |
I edited the title to reflect the addition of getstakeinfo and to mention addticket. The problems really lie with the original implementation of the stake code in wallet. That code has been improved and refactored and we need to cope with the changes. Per decred/dcrwallet#913: Added tickets are auxiliary to transaction history and do not appear in getstakeinfo stats. Current status:
|
Not actively working on this at the moment but it still needs to be done. |
The number of redeem scripts (from
listscripts
) and tickets (fromgettickets
) may be the same on all wallets, but it is possible forgetstakeinfo
to not match for several reasons that are difficult to rectify.One is that if the operator has performed
addtickets
on the wallets at some point, it is necessary to do add the same tickets (until they've expired) on newly added wallets to get the number of"live"
tickets ingetstakeinfo
to match between wallets. This makes it necessary to manually collect every added ticket in a list somewhere so that they can be added in the event of wallet addition or disaster recovery.In the same case as above, even after doing
addtickets
(for every invalid ticket ever added), the"voted"
number on the new wallet does not catch up with the elder wallets.Perhaps this should be a dcrwallet issue, but perhaps it's time to workaround this in dcrstakepool given the new stakepoold arch changes.
The text was updated successfully, but these errors were encountered: