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.
block date
398784 - Tue Jan 5 04:47:12 UTC 2016
415400 - Wed Feb 3 01:07:12 UTC 2016
432016 - Wed Mar 2 21:27:12 UTC 2016
448632 - Thu Mar 31 17:47:12 UTC 2016
465248 - Fri Apr 29 14:07:12 UTC 2016
481864 - Sat May 28 10:27:12 UTC 2016
498480 - Sun Jun 26 06:47:12 UTC 2016
515096 - Mon Jul 25 03:07:12 UTC 2016
531712 - Mon Aug 22 23:27:12 UTC 2016
548328 - Tue Sep 20 19:47:12 UTC 2016
564944 - Wed Oct 19 16:07:12 UTC 2016
581560 - Thu Nov 17 12:27:12 UTC 2016
598176 - Fri Dec 16 08:47:12 UTC 2016
here's the script and math
# 16616 / 576 = 28.8472 * 24 = 692.33
D0=$(TZ=UTC date --date="$(date --date="2015-12-07T08:27:12+0000")");
for block in `seq 398784 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.