nikeshnazareth verifiable-voting issues

nikeshnazareth / verifiable-voting

A verifiable voting system built using Ethereum and IPFS

MIT License

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Standardise RXJS operator imports

#41 nikeshnazareth opened 5 years ago
1
CompleteRegistration form throws excessive errors

#40 nikeshnazareth opened 5 years ago
0
"Buffer is not defined" when creating a vote

#39 nikeshnazareth opened 5 years ago
2
Callstack size exceeded

#38 nikeshnazareth closed 5 years ago
2
Use https when posting to IPFS

#37 nikeshnazareth closed 5 years ago
1
There should be a splash screen requesting that the user install and configure MetaMask instead of an error bar

#36 nikeshnazareth opened 6 years ago
0
The tslint deprecation rule should be changed to { "severity": "warn" }

#35 nikeshnazareth opened 6 years ago
1
When you switch between votes with one of the phase-specific forms open, it remains open even if that phase is disabled in the new vote

#34 nikeshnazareth opened 6 years ago
0
The minimum and maximum validation values for the DatetimePickerComponent should constrain the UI of the individual elements

#33 nikeshnazareth opened 6 years ago
1
There should be a component to allow the Registration Authority to complete registrations

#32 nikeshnazareth closed 5 years ago
0
There should be a component to display transactions while they are waiting to be mined

#31 nikeshnazareth closed 6 years ago
2
The vote timeframes should include minute resolution and timezone support

#30 nikeshnazareth closed 6 years ago
0
The vote creation form should start with all the stages closed

#29 nikeshnazareth opened 6 years ago
0
The wrapRetrieval and throwIfEmpty functions in VoteRetreivalService should be written as custom rxjs operators

#28 nikeshnazareth closed 5 years ago
0
There should be a protocol for when a voter submits an invalid or irretrievable vote

#27 nikeshnazareth opened 6 years ago
1
Move the IPFS hash resolve functionality from the VoteRetrievalService to the IPFS Service

#26 nikeshnazareth closed 6 years ago
0
There should be a protocol for when a voter registers with an invalid or irretrievable blinded address

#25 nikeshnazareth opened 6 years ago
0
Replace the writeonly blockchain storage with events

#24 nikeshnazareth opened 6 years ago
1
Mobile users should see a tailored design

#23 nikeshnazareth opened 6 years ago
1
The AnonymousVoting contract events are re-emmited for every subscriber. They should be multicast

#22 nikeshnazareth closed 6 years ago
0
The VoteRetrievalService should not have a separate function for blind signatures

#21 nikeshnazareth closed 6 years ago
1
Verify that the blind signature matches the blinded address before allowing the user to vote

#20 nikeshnazareth closed 6 years ago
0
Confirm the blinding factor is correct before allowing the user to submit their vote

#19 nikeshnazareth opened 6 years ago
0
The VoteRetrievalService should calculate the phase based on the deadlines. Downstream components should not know about the deadlines

#18 nikeshnazareth closed 6 years ago
1
There should be a component to view the results of a vote

#17 nikeshnazareth closed 6 years ago
0
There should be a component to let a voter vote

#16 nikeshnazareth closed 6 years ago
0
VoteRetrieval service puts retrieving/unavailable status values directly into strings, but uses IDynamicValue for other types. It should use IDynamicValue for all types

#15 nikeshnazareth closed 6 years ago
0
The error snackbar should permit closing errors and navigation between them

#14 nikeshnazareth closed 6 years ago
1
RSA blinded messages should be padded appropriately before applying the blinding factor

#13 nikeshnazareth opened 6 years ago
1
There should be a component to let a voter register their blinded address

#12 nikeshnazareth closed 6 years ago
0
ListVotesComponent should update the phase at the appropriate time (in addition to when the phase is updated in the contract)

#11 nikeshnazareth closed 6 years ago
0
VoteComponent should show the full details of an existing vote

#10 nikeshnazareth closed 6 years ago
0
When a vote is launched, the form content is cleared but the mat-input components are styled liked invalid controls

#9 nikeshnazareth opened 6 years ago
0
ListVotes components should display topic and status

#8 nikeshnazareth closed 6 years ago
0
The LaunchVote component should accept topic, timeframes, candidates, eligibility criteria and RSA public key as the vote parameters

#7 nikeshnazareth closed 6 years ago
0
There should be a default eligibility criteria contract

#6 nikeshnazareth closed 6 years ago
0
AnonymousVoting contract should enforce phases

#5 nikeshnazareth closed 6 years ago
0
ListVotes components retrieves all contract details every time a new vote is added

#4 nikeshnazareth closed 6 years ago
1
Anyone should be able to read the vote parameters from the hash stored on Ethereum

#3 nikeshnazareth closed 6 years ago
0
Organiser should be able to add vote parameters IPFS hash to Ethereum

#2 nikeshnazareth closed 6 years ago
0
Organiser should be able to add vote parameters to IPFS

#1 nikeshnazareth closed 6 years ago
0