Now live: https://www.dashcentral.org/p/Adaptive-Proposal-Fees
Introduction
As many of you know, there has been much discussion regarding the current 5 dash proposal fee. Although 1DPF (1 Dash Proposal Fees) was rejected, the debate clearly divided opinion.
The original 5 dash proposal fee was introduced as a mechanism to reduce spam. To date, this has worked relatively successfully. However, the current US dollar price of dash is leading some people to question if the high fee is stifling progress. OTOH, some MNOs believe the high fee acts as a filter; attracting larger and more professional projects.
Personally, although I favour a lower fee, I fully appreciate both sides of this argument. With this in mind, I am proposing what I believe to be a fair and sustainable solution.
Please keep in mind, over time, this proposal would produce some very valuable historic data regarding MNO sentiment and perhaps substantiate (or disprove) any correlation between proposals and their fees.
Note: To help those unfamiliar, this proposal also includes a brief explanation of how median averages work and why it’s well suited for this particular problem.
(This solution is using the median average, not the mean average! See explanation below)
Feasibility
As you know, we can not force core devs to enact this proposal, but your yes votes will send them a clear message. Official dash developer @UdjinM6 has indicated that this proposal looks, on the face of it, technically possible. In the short term this could be implemented as a traditional spork. However, a longer term solution might be to develop a “masternode spork”, which would be useful for many other applications / parameters.
Keep It Simple Stupid
Alternative solutions have been discussed, such as criteria based refunds and USD pegs. However, those discussions further fragmented opinion. By denominating in dash, we show no favour to one fiat currency over another. Each MNO understands the price of dash in their local currency, and they are free to adapt their vote accordingly. By denominating in dash, we are all on the same page. This is the solution of least resistance.
MNOs are being paid to make decisions and this is a very simple procedure for an MNO to voluntarily carry out each month, with the potential to be even easier through a web interface such as Dash Central et al.
Solution
Once a month, MNOs can voluntarily submit their preferred proposal fee. At the time of the Superblock, the median average will be used for the new month. A console command would be linked to a spork and look something like this:
gobject vote-many proposal-fee 5
As a voting command, MNOs would be free to change their vote within the usual constraints.
As a safety measure, at least 2% of all masternodes would need to vote, thus ensuring a good pool of diversity (2% of 4400 MNs = 88 MNs). In the extreme case of not meeting this minimum, the fee would continue as the previous month. (no one voting on a proposal fee would be symptomatic of a much bigger problem)
How to calculate the median average
All votes are placed in ascending order. For example, here are 9 votes:
1 1 3 4 5 5 5 9 10
The middle of this set is the median average. In the above example, 5 is the median average.
If there is an even set of numbers, the two middle numbers are averaged in the traditional way. That is to say, the two middle numbers are added together and divided by two. In the following example, 4 and 5 are the two middle numbers:
1 1 1 3 4 5 5 5 9 10
The average is therefore (4 + 5) / 2 = 4.5
For an alternative explanation, please see http://www.mathsisfun.com/median.html
The median average is especially good at filtering out extreme values. Let’s say, for example, there are 100 votes with 40 rogue values (extremely high or low), yet those values would still not reach the middle of the set.
Introduction
As many of you know, there has been much discussion regarding the current 5 dash proposal fee. Although 1DPF (1 Dash Proposal Fees) was rejected, the debate clearly divided opinion.
The original 5 dash proposal fee was introduced as a mechanism to reduce spam. To date, this has worked relatively successfully. However, the current US dollar price of dash is leading some people to question if the high fee is stifling progress. OTOH, some MNOs believe the high fee acts as a filter; attracting larger and more professional projects.
Personally, although I favour a lower fee, I fully appreciate both sides of this argument. With this in mind, I am proposing what I believe to be a fair and sustainable solution.
Please keep in mind, over time, this proposal would produce some very valuable historic data regarding MNO sentiment and perhaps substantiate (or disprove) any correlation between proposals and their fees.
Note: To help those unfamiliar, this proposal also includes a brief explanation of how median averages work and why it’s well suited for this particular problem.
(This solution is using the median average, not the mean average! See explanation below)
Feasibility
As you know, we can not force core devs to enact this proposal, but your yes votes will send them a clear message. Official dash developer @UdjinM6 has indicated that this proposal looks, on the face of it, technically possible. In the short term this could be implemented as a traditional spork. However, a longer term solution might be to develop a “masternode spork”, which would be useful for many other applications / parameters.
Keep It Simple Stupid
Alternative solutions have been discussed, such as criteria based refunds and USD pegs. However, those discussions further fragmented opinion. By denominating in dash, we show no favour to one fiat currency over another. Each MNO understands the price of dash in their local currency, and they are free to adapt their vote accordingly. By denominating in dash, we are all on the same page. This is the solution of least resistance.
MNOs are being paid to make decisions and this is a very simple procedure for an MNO to voluntarily carry out each month, with the potential to be even easier through a web interface such as Dash Central et al.
Solution
Once a month, MNOs can voluntarily submit their preferred proposal fee. At the time of the Superblock, the median average will be used for the new month. A console command would be linked to a spork and look something like this:
gobject vote-many proposal-fee 5
As a voting command, MNOs would be free to change their vote within the usual constraints.
As a safety measure, at least 2% of all masternodes would need to vote, thus ensuring a good pool of diversity (2% of 4400 MNs = 88 MNs). In the extreme case of not meeting this minimum, the fee would continue as the previous month. (no one voting on a proposal fee would be symptomatic of a much bigger problem)
How to calculate the median average
All votes are placed in ascending order. For example, here are 9 votes:
1 1 3 4 5 5 5 9 10
The middle of this set is the median average. In the above example, 5 is the median average.
If there is an even set of numbers, the two middle numbers are averaged in the traditional way. That is to say, the two middle numbers are added together and divided by two. In the following example, 4 and 5 are the two middle numbers:
1 1 1 3 4 5 5 5 9 10
The average is therefore (4 + 5) / 2 = 4.5
For an alternative explanation, please see http://www.mathsisfun.com/median.html
The median average is especially good at filtering out extreme values. Let’s say, for example, there are 100 votes with 40 rogue values (extremely high or low), yet those values would still not reach the middle of the set.
Last edited:
