I find it strange that you want to *continue* here. Last i checked we were discussing the rules for the voting system. I think the simplest and fairest rule to ensure that a majority is what has voted, not a highly organized minority is to require a 60% voter turn  out . Your suggestion to keep the vote between yes/no makes the assumption that there will only ever be two options, which i think will not be the case. So now with 60% of eligible voters having cast votes, i think that we can then use a simple tally. We can of course go a little further and attempt to apply something like STV or an alternative vote system, depending on user response to this post.

The launch of v 2.0 is imminent, but I'd like to bring in some new ideas.

I'd like to start by dropping a zero, meaning that if v 1.0 supply is 30 M , in v 2,0 this will be represented as 3 M .
Also i will reduce the total supply from the v 1.0 210 M , to 6 M in v 2.0.
The new system is divided into three components, client, server (basenode) and web.
Client is for all users, servers are for those who wish to provide services and the web is a unified summary view of the system, which at this point means a web view of loans and perhaps a fiat portal. Server and web end will remain closed source for the foreseeable future. 

The cost of this last development phase was mostly covered by the sell off we did of the 6 M I had been holding that has originally been stored @ Empoex. We have an additional 3-4 phases to go and i wanted to try and fund them in the launch of v 2.0 once and for all. To this end, i have suggested an ICO @ launch. While the details are as yet unclear, the general idea is that we set a base price, based on the above mentioned changes and put the coins up for sale. The proceeds of which depending on how much are raised, will be put to work towards building the next phases until exhausted.

Asking for another dev's assistance in certain areas i am not so adept is much easier when i can wave some coin in their faces