demo
Well-known member
Something maybe worth bearing in mind, increasing the fee is much more difficult than reducing it because it basically means a fork and there's more incentive to keep the lower fee. That's something best avoided imho, I'd rather see folks grouping together with similar projects and splitting the fee or have major proposals to fund multiple minor projects and base a fee mechanism on how that pans out than to see a change made that could have harmful consequences and be difficult to reverse.
The budget is not only for submitting implementation proposals. It can also be used for submitting simple questions, asking the masternodes about their principles .
For example a principle question may be : "Do you like all masternodes to have a static IP?" or "Do you want to implement a proof of identification for the masternodes?".
You have to encourage people to ask the masternodes about their principles, thats why a proposal fee should be kept low.
Of course the masternodes should not be enforced to answer to the questions, thats why a mininum participation (currently set to 10%) should be there and only if this threshold is bypassed the reimbursement of the proposal fee should be payed.
Finaly the principle question after beeing finilized, the question should remain and continue to get voted, because the masternodes may change their mind in specific principle after one year or so, and this should be visible to everybody.
Last edited: