-
Notifications
You must be signed in to change notification settings - Fork 1
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
Security Considerations #64
Comments
Contract address is used in signature EIP712 domain separator therefore vote can't be reused for different voting contract because the signature won't match |
Please see more properties at https://github.com/status-im/dappconnect-voting-sdk |
what is |
#66 looks good, I think it's a question of terminology. |
Few issues I noticed when looking at the security of the SDK.
I started to write a document: https://github.com/status-im/dappconnect-voting-sdk#security-considerations
1. Election start
if an account calls
initializeVotingRoom
withvoteAmount: 0
then it can starts an election without holding any token.Only token holder MUST be able to start an election.
2. Cross-contract votes
As far as I can see, a vote can be re-used for 2 different voting contract (same or different ERC-20 tokens) as the vote only the voter account, room id (indexed per voting contract), voting value and token amount.
The voting contract address is NOT part of the vote. I believe it must be added to stop users re-using votes for election that have same index across different contracts (e.g. user participate to 2 different DAOs for 2 different ERC20 token that use this SDK).
The text was updated successfully, but these errors were encountered: