You may think that there is no way to vote the numbers in the current budget voting system. Well, there is!

So, how can we vote the numbers in the current budget system?

Simple, you have to use the

**TERNARY or ΤRINARY or ****BASE3**** NUMERAL system**
If you make the assumption that NO_VOTE=0, ABSTAIN_VOTE=1, and YES_VOTE=2 , then you can vote numbers from 0-2.

if you cast TWO proposals (at the cost of 2 dash proposal fee) under the TERNARY system, then you can vote numbers from 0-8

if you cast THREE proposals (at the cost of 3 dash proposal fee) under the TERNARY system, then you can vote numbers from 0-26.

So if you want to vote from 0 to 100 and you afford to pay for 3 proposals, you can divide (100-0)/26=3.84. Your

**chunk** is 3.84 and thus if the average of the voting result of the budget vote is 1 then 3.84 is voted, if the average result of the budget vote is 10 then 38.4 is voted, if the average result of budget vote is 15 then 57.6 is voted e.t.c.

By adding a fourth proposal, you can have 80 divisions, by adding a fifth proposal you can have 242 divisions, so you can increase the granularity of your vote.

Finally,

**you can also use the ****BASE4**** numeral system **(DIDNT_VOTE=0, ABSTAIN_VOTE=1, NO_VOTE=2 and YES_VOTE=3). You make the assumption that the people who voted in at least one numeral proposal, declare a 0 vote to all the rest proposals that are associated to it.

Example: by using the 4base, with just 2 proposals (at the cost of 2 dash proposal fee) you can have 15-1=14 divisions (because the 00 vote is not a valid vote in that case, and it is used to calculate the voting participation).

__proposal1, proposal2__
didnt vote, didnt vote = 00 base4 = decimal 0 (didnt vote at all, invalid number. This is used to calculate abstention and thus decide whether the voting result is legitimate.)

didnt vote, abstain = 01 base4 = decimal 1

didnt vote, no = 02 base4 = decimal 2

didnt vote, yes = 03 base4 = decimal 3

abstain, didnt vote = 10 base4 = decimal 4

abstain, abstain = 11 base4 = decimal 5

abstain, no = 12 base4 = decimal 6

abstain, yes = 13 base4 = decimal 7

no , didnt vote = 20 base4 = decimal 8

no, abstain = 21 base4 = decimal 9

no, no = 22 base4 = decimal 10

no, yes = 23 base4 = decimal 11

yes, didnt vote = 30 base4 =decimal 12

yes, abstain = 31 base4 =decimal 13

yes, no = 32 base4 = decimal 14

yes, yes = 33 base4 = decimal 15

**Warning:** If you want the masternodes to be able to fully rollback and change their vote, then BASE3 is more suitable, because in BASE4 when you vote 1(abstain), 2(no) or 3(yes) you cannot rollback to 0(didnt vote). This due to the code written by DCG which does not allow the masternodes to undo their vote.

**Warning 2: **For both Base4 and Base3 you may want to change the semantics of the vote and make it for example 0=no, 1=didnt_vote, 2=abstain, 3=yes or whatever combination, in case you can guess what the majority of the masternodes will vote. In case you can guess succesfully and rearrange the semantics so that "yes" is the most probable, this will resut for you to pay less proposal fee.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Here follows a practical application of the above:

You have done some work for the community but you dont know how much your job worths (or you dont want to say it). In that case you can ask the masternodes to vote the numbers about it ( look also at

*"Vote The Numbers (mnowatch.org)**"* ). When the compensation number is defined/voted, you can then ask again the masternodes (in another proposal) for the final yes/no on the specific number, and get paid from the budget.

By applying BASE4, and in case you are using 3 proposals (at the cost of 3 dash proposal fee) , you can have chunks of 4592/62=74 dash. Assuming that you define the payment range from 0 to 4592 dash (the whole monthly budget), every masternode is allowed to vote for your reward to be either 0 dash or 74 dash or 148 dash or 222 dash or 296 dash e.t.c. ... or 4592 dash. This is the

**single** numerical vote.

You also have to define the method that will be used to extract the result from the numerical votes. There are some available methods you can arbitrarily choose: the most voted number, the median average, the mean average, the majority, the absolute majority, the strong majority, the unanimity. In case you dont even want to arbitrarily select that method, you can ask the masternodes about it , by issuing another numerical vote that will allow the masternodes to select among available methods. The winner method in that case should respect itself (the

bold rule). This is the

**double** numerical vote.

Finnaly you have to decide the minimum voting participation that makes a result legitimate. You can arbitrarily decide that, or you can again ask the masternodes about it. This requires yet another numerical vote to be made, that also depends on the aforementioned bold rule. This is the

**triple** numerical vote.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

There are 10 kinds of humans. These who understand the above, and these who do not.

Do NOT follow the hollow. Vote the numbers!