Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes use of the
ticketinfo
RPC added to dcrwallet to:Consistency checking
Consistency checks are run immediately on vspd startup and then once every 30 minutes (Closes #46). Consistency checking is a two step process:
ticketinfo
on each voting wallet to ensure all of the wallets are aware of all of the ticketsSet ticket outcome
Using
ticketinfo
allows vspd to determine when a ticket is no longer votable, either because it has already voted or because it has been revoked. This information is now stored in the vspd database. Theticketinfo
RPC does not distinguish between missed and expired tickets, and so vspd simply buckets both of these intorevoked
.This occurs each time a block is connected by the local dcrd instance, which provides a regular check on the status of dcrwallet RPC connections (Closes #103).
Counts of
Voting
/Voted
/Revoked
tickets are now reported on both the web front-end and through the/vspinfo
API call. This replaces the previous counts ofTotal tickets
andFee confirmed tickets
. Tickets with unconfirmed fees are no longer reported.