• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

VOTE2:Dash being locked by MO according the result of VOTE1 should be 70%, so what shall we do?

We have to increase the dash being locked by MO to reach the result of vote1(=70%), so what we do?

  • Each masternode in order to remain a masternode should cost more than 1000 dash.

    Votes: 1 33.3%
  • Decrease the price for NEW masternodes, in order to attract new masternodes and reach 70% limit.

    Votes: 1 33.3%
  • other

    Votes: 1 33.3%

  • Total voters
    3

demo

Well-known member
This vote depends on vote1, and has been initialized and appears because of this code.

According to the current result of vote1, we have to increase the dash being locked by MO in order to reach 70%.

So what shall we do?

I can think of 2 solutions:


  1. In order to reach the decided 70% of dash locked, every masternode should cost more than 1000 dash.
  2. Decrease the price for NEW masternodes, in order to attract new masternodes and reach 70% limit.
 
Last edited:
If you can think of another solution in order to reach this 70%, then please just tell the solution instead of voting "other" (and I will add your solution as vote option)
 
Last edited:
CURRENT RESULT
<
vote2>
VOTE TITLE: We have to increase the dash being locked by MO to reach the result of vote1(=70%), so what shall we do?
Each masternode in order to remain a masternode should cost more than 1000 dash.
0 vote(s) 0.0%
Decrease the price for NEW masternodes, in order to attract new masternodes and reach 70% limit. 1 vote(s) 50.0%
other 1 vote(s) 50.0%
</vote>
<double vote history for vote2>
VOTE TITLE: What the selection process of the above (and this one) vote should be?
OPTION1: most voted 1 vote(s) 50.0%
OPTION2:majority 0 vote(s) 0.0%
OPTION3: other 1 vote(s) 50.0%
</double vote history>
<selection process>
  • The selection process is decided to be "the most voted" according to the rule :"Each selection process in order to be selected should initialy respect itself, then the most loved selection process is selected ".
  • The "other" option is NOT the most loved one, so a decision can be made.
  • The most voted option is: Decrease the price for NEW masternodes, in order to attract new masternodes and reach the desired 70% limit. so this is the current decision (although unstable one as long as not many people voted here yet).
</selection process>

The proponents of the solution 70% should design the voting tree. The proponents of the option "decrease the price of NEW Masternodes in order be able to reach 70%", they should not only propose it but also implement the solution, and the implemented code should be allowed to run in the runtime (if ignited as the current decision of vote2 of course)

As you can see, if there is no code implemented , then the vote (or the option of the vote) does not appear at all. If you have not coded what you propose, then your option is invalid. This is logical, as long as the system affects the runtime, you should not be allowed to propose something without having coded it first. You first have to code your proposed solution, then you are allowed to propose it as an option into a vote (which vote resides of course into the appropriate branch of the voting tree), and then if your option is voted as a decision then your code can starts running.

I know that very few people understand what I am talking about, but anyway I had to tell those things.
 
Last edited:
CURRENT RESULT
<
vote2>
VOTE TITLE: We have to increase the dash being locked by MO to reach the result of vote1(=70%), so what shall we do?
Each masternode in order to remain a masternode should cost more than 1000 dash.
1 vote(s) 33.3%
Decrease the price for NEW masternodes, in order to attract new masternodes and reach 70% limit. 1 vote(s) 33.3%
other 1 vote(s) 33.3%
</vote>
<double vote history for vote2>
VOTE TITLE: What the selection process of the above (and this one) vote should be?
OPTION1: most voted and if draw the first voted 1 vote(s) 33.3%
OPTION2: most voted (which is acctualy the same as mode average) 1 vote(s) 33.3%
OPTION3: majority (50%+1 of votes) 0 vote(s) 0.0%
OPTION3: strong majority (2/3 of votes) 0 vote(s) 0.0%
OPTION4: other 1 vote(s) 33.3%
</double vote history>
<selection process>
  • The selection process is decided to be "most voted and if draw the first voted " according to the rule :"Each selection process in order to be selected should initialy respect itself, then the most loved selection process is selected ".
  • The "other" option is NOT the most loved one, so a decision can be made.
  • The most voted options are two, it is a draw, but the first voted is: Decrease the price for NEW masternodes, in order to attract new masternodes and reach the desired 70% limit. so this is the current decision (although unstable decision as long as not many people voted here yet, this is also because the correct vote is not the "double vote" <number, selection process> but the "triple vote" <number, selection process, minimum participation percentage> but I will explain this later on)
</selection process>
 
Last edited:
Back
Top