Double-post, if this still is (it isn't!), to deal with Blockchainy mechanics.
Complaints about electronic voting tend to accumulate to "How do I know that when I've cast my vote for Foo, it won't get marked against Bar?"... With apparent worries that machines were hacked to change the on-screen vote of people, in 2016 (ignoring the fact that this would be an ultra-naive way to do it, if you had any proper access to the system. Best to say "Yup, you voted Foo!" on-screen but make it tally fror Bar anyway).
Also, people can be worried that They can tell how they vote (or, for people not worried, others might be worried that a Them might be rewarding people who are proven to have voted Their desired way). Which requires anonimisation, and so a solution to the first problem of having a searchable index for voter to ask "who do you think I voted for?" is also not a solution in that raw form.
I suspect Blockchain is being touted because it (at one level) takes data and mixes it into another mass of previously verified data in a verifiable way such that specific queries can be made of it (if necessary) without having one big plaintext infodump (ab)usable by a certain kind of entity.
Though much of that facility is just basically a massively-salted hashing function. Which isn't anything new. And doesn't stop the hacked/pre-biased system from finding ways to tally things up 'wrongly' but give a reassuring 'right' answer, I'm sure.
However, this is how I'd do it, knowing that I'm not spending enough time trying to examine the pitfalls I undoubtedly am building in:
Actually, deleted it. It's just saying what others have said it might be, but with too many words.
Also this was designed for official machines, easily controlled and auditable, not AppStore dowloaded one-vote-each connections to the node.