Quote from: Minotaur26 on December 17, 2015, 01:48:58 AM

Just to make sure we are all on the same page, this is how the system currently works:

From dashninja:

A budget proposal is valid if the fee was payed and it was submitted to peers successfully.

A budget proposal is established when it is older than 1 day.

A budget proposal is alloted (will get paid on next super-block and is in the budgets projection list) when Yea votes minus Nay votes is more than 10% of total masternodes.

The system is designed to resolve controversy, the way it works the yeas in the proposal have to win the nays by at least 10% of the network. If there is a polemic proposal where 10% of the network says No then you need at least 20% of the network to say yes for it to get approved for a total 30% participation. It self adjusts and I don't think this is well understood. Hope this helps.

Quote from: moocowmoo on December 18, 2015, 07:15:11 AM

Quote from: TanteStefana2 on December 17, 2015, 07:32:16 PM

Also, we don't have enough time to review proposals. Generally, people are just giving us a couple of weeks, that's not enough to discuss and argue. I think, for this to work best, we should do this in 2 steps. First, gather the proposals, then spend 1 month discussing them before they're open for voting. Then vote.

There's no need to rush any vote if the budget proposal is planned correctly.
The only time constraints on a proposal's voting window are defined by the submitter.
It's perfectly valid to submit a proposal that starts getting paid at a later cycle(s).

In fact, I'd encourage future submitters to do just that, *especially* if it is a one-time payment.

Here are next years cycle start blocks and approximate dates. Set your payment-start block's accordingly.

Code:

block date
382168 - Sat Jan 16 01:20:00 UTC 2016
398784 - Sat Feb 13 21:40:00 UTC 2016
415400 - Sun Mar 13 18:00:00 UTC 2016
432016 - Mon Apr 11 14:20:00 UTC 2016
448632 - Tue May 10 10:40:00 UTC 2016
465248 - Wed Jun 8 07:00:00 UTC 2016
481864 - Thu Jul 7 03:20:00 UTC 2016
498480 - Thu Aug 4 23:40:00 UTC 2016
515096 - Fri Sep 2 20:00:00 UTC 2016
531712 - Sat Oct 1 16:20:00 UTC 2016
548328 - Sun Oct 30 12:40:00 UTC 2016
564944 - Mon Nov 28 09:00:00 UTC 2016
581560 - Tue Dec 27 05:20:00 UTC 2016

here's the script and math

Code:

# 16616 / 576 = 28.8472 * 24 = 692.33
D0=$(TZ=UTC date --date="$(date --date="2015-12-07T08:27:12+0000")");
for block in `seq 382168 16616 $((382168 + (16616*24)))`;
   do DD=$(TZ=UTC date --date="$(date --date="$D0") +692 hours +20 minutes");
   D0=$DD;
   echo "$block - $DD";
done

Also, I'd like to remind everybody of some important differences from typical elections that Dash's voting system has:
(taken from masternode-budget.cpp)

- Votes are counted every 16616 blocks
- Votes can be recast at any time
- Budget proposals remain on the network until:
either 340 more nay votes than yay votes are cast (10% of total masternodes)
or the proposal end block is reached
- Approved budgets are paid in order of yay - nay votes
- Approved budgets can be nullified at any time by recasting votes

Also, A bit of rumor control about "Evan controlling the budget system":

Evan doesn't have enough masternodes online to pass anything.
Neither do I.

Even working together we couldn't vote the required 10%.

From what I've gathered analyzing vote timestamps only otoh has enough
masternodes provisioned to cast enough votes to pass a budget item.

But even with approximately 600 masternodes (maybe less today), it would only
take 261 no votes to prevent the budget item from passing.

Additionally, the budget allocation is disbursed in order of yay - nay votes.
So, even if somebody did sneak a budget item in at the last second, it would
only be processed after all other approved budgets had been funded.

--

I hope this post helps to dispel any concern about dash being controlled by
whales.

The way the system is set up, what is good for the currency will
trump any few individuals' will to power.

This is valuable info and it's gonna get buried deep in this forum.
I would suggest someone includes this info in the official documentation.
The budget system wiki is very, very incomplete.