ahh Voting!
one of my favorite discussions ;-)

Currently read many good aspects here!
I think we need to consider most of them in beta Client.
More and more it becomes clear that there is not THE ONE way for VS.
But there are different poll-categories, e.g "assets-polls" is different category as "best button color-polls".

The poll initiator should be able to choose boundary conditions depending on poll-topic.
The poll boundary conditions need to be transparent during run time.
To be more constructive lets try to collect some "Voting Models":

general options:
- min. permitted Account Deposit
- min. permitted Account age (Blocks)
- poll duration (Blocks)
- Voting Fee

Voting Models
- 1 NXT        ==   1 Vote  { vote = Func(accountBalance) }
- 1 Account  ==  1 Vote   { vote = Func(accountBalance) =  0.5 * accountBalance}
- 1 Account  ==  1 Vote   { Jcsarokrin Biometric Authenification: http://juliansarokin.com/100-years-the-future-of-government/}
- 1 NXT        ==   x Vote  { x = Func(accountBalance) =  polynom * accountBalance}
- coolmist  {votingweight = ( 1 / similarity ) ^ (4/3) * (accountbalance)^(1/3) * (accountage)^2 (timesvoted)^(3/2)}


no claim to completeness!


We need to discuss selection options too:
[true]    [false]    [abstention]
I think [abstention] provides an important information too.
E.g. a high count of [abstention] tells the poll creator "interesting question buddy, but not this way!!!" ...