Skip to content

Better threat different offchain signed votes for same proposal  #7

@3esmit

Description

@3esmit

Currently, signed votes are included with no verification to reduce the cost. This should stay as it is.

The problem with this is that it allows a voter to submit 2 different votes, and the tabulation would get into a race condition.

Currently the first tabulated would be the accepted. The retabulation is prevented by this line:

require(voteMap[_voter] == Vote.Null, "Already voted");

This is a problem because delegates could vote for something and later change their minds, making community not be able to quickly follow their actions. Also putting the tabulation in a unpredictable outcome for that account influence (and delegated influence).

Its not a security problem, however it can help delegates to mislead their vote at votingPeriod.

A option would be to burn the vote (or make it a blank vote). The problem is if there is already indirect influence claimed.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestquestionFurther information is requested

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions