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

multi: Add timestamp to ticket vote. #1395

Merged
merged 1 commit into from
Apr 12, 2021
Merged

multi: Add timestamp to ticket vote. #1395

merged 1 commit into from
Apr 12, 2021

Conversation

lukebp
Copy link
Member

@lukebp lukebp commented Apr 12, 2021

This diff adds a unix timestamp to the cast vote details that is saved
to disk when a ticket vote is cast.

The timestamp was not included in the git backend ticket votes because
the git backend only flushed the vote journals once per hour. This means
that you could only determine if a vote was cast within a +/- 60 minute
period. Adding the timestamp to the vote would have provided granular
details that could be used to correlate blocks of votes to their owner.

This argument does not apply to the tstore backend because tlog already
provides a granular timestamp for each vote leaf. Since the data is
already public it should be returned through the API so that clients
like dcrdata, who use the data to construct vote graphs, do not need to
walk the tlog tree manually in order to parse the timestamp.

This diff adds a unix timestamp to the cast vote details that is saved
to disk when a ticket vote is cast.

The timestamp was not included in the git backend ticket votes because
the git backend only flushed the vote journals once per hour. This means
that you could only determine if a vote was cast within a +/- 60 minute
period. Adding the timestamp to the vote provided granular details that
could be used to correlate blocks of votes to their owner.

This argument does not apply to the tstore backend because tlog already
provides a granular timestamp for each vote leaf. Since the data is
already public it should be returned through the API so that clients
like dcrdata, who use the data to construct vote graphs, do not need to
walk the tlog tree manually in order to parse the timestamp.
@lukebp lukebp merged commit 458f37d into decred:master Apr 12, 2021
@marcopeereboom
Copy link
Member

If correlation is a concern, use the vote trickler in politeiavoter.

politeiavoter now has a completely random voter that bunches votes and whatnot so the concern of correlating has been somewhat alleviated.

@lukebp lukebp deleted the votets branch April 29, 2021 20:49
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

Successfully merging this pull request may close these issues.

2 participants