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

Reduce the proposal fee to one dash

Demo, the testnet is facing some kind of environmental issue where nodes get POSE banned when they should not, this reason is causing hold up of the plan to deploy to mainnet, however, the plan is still to go ahead and fork the new code in test while we try different things to address this issue.

Why are you trying to find excuses for the agents?
The code was ready, the network commanded, the version 18 should have contained ONLY the reduction of the proposal fee.

But the agents intervened, they added a tone of irrelevant changes to the version 18, probably they also added the bug you are claiming, so that the comandment of the network to be delayed for one whole year (and maybe more, I afraid that the agents may find more excuses and next year we will celebrate our second anniversary).

Under no circumstances should the network be allowed to decide essential things, the decision power should remain among the agents, and this is another red line of the agents. No one is allowed to cross their red lines, the agents will use whatever cunning, excuse, deceit, money or violence in order to preserve their stinky/deadly territory.


Red-Line-Story-Morrison.jpg

51vtK3MyD7L._AC_.jpg
 
Last edited:
Why are you trying to find excuses for the agents?
The code was ready, the network commanded, the version 18 should have contained ONLY the reduction of the proposal fee.

I don't recall this being the case, I always thought it was supposed to slot in with whatever was planned for v18, however, quorum rotations was not planned for v18 and should not have been shoved in and it is the reason for the release delay.

But the agents intervened, they added a tone of irrelevant changes to the version 18, probably they also added the bug you are claiming, so that the commandment of the network to be delayed for one whole year (and maybe more, I afraid that the agents may find more excuses and next year we will celebrate our second anniversary).

No one intentionally adds a bug, that's super paranoid, I don't consider any of the changes irrelevant, but some could have been held over to a later release for sure.
 
quorum rotations was not planned for v18 and should not have been shoved in and it is the reason for the release delay.
No one intentionally adds a bug, that's super paranoid, I don't consider any of the changes irrelevant, but some could have been held over to a later release for sure.

Quorum rotations was not planned for v18, and quorum rotations is the reason of the bug and of the delay. Does the bear shit in the woods?

The agents intentionally included something non planned and very complex into the v18 release, something easy to inject a bug in it, in order to cause the delay.

The agents dont like the network to compel changes to their code. This is an old story , it was happening even before your arrival here in dash @xkcd....and it keeps happening.
 
Last edited:
Quorum rotations was not planned for v18, and quorum rotations is the reason of the bug and of the delay. Does the bear shit in the woods?

The agents intentionally included something non planned and very complex into the v18 release, something easy to inject a bug in it, in order to cause the delay.

The agents dont like the network to compel changes to their code. This is an old story , it was happening even before your arrival here in dash @xkcd....and it keeps happening.


Two simple questions.

1) Who decided to include the non planned Quorum rotations into the v18 release?
2) Assuming good faith, why dont you remove the buggy Quorum rotations from the v18 release, and release v18 without it?

Can somebody answer?

"Thou lovest all devouring words, O thou deceitful tongue. Why do you brag of evil, Big Man?"
 
Last edited:
Simply terrible management. The change was one or two lines of code. That single change should of immediately triggered a new release but the poor decision was made to include other "improvements". The DAO as a whole has suffered because of that one decision. From now on, we must give DAO modifications the priority they deserve, you can apply these other "improvements" some other time.

And by coincidence, the Thor integration was approved then delayed and modified since when exactly?? True, the agents employed to delay and kill dash are working hard.
 
Simply terrible management. The change was one or two lines of code. That single change should of immediately triggered a new release but the poor decision was made to include other "improvements". The DAO as a whole has suffered because of that one decision. From now on, we must give DAO modifications the priority they deserve, you can apply these other "improvements" some other time.

And by coincidence, the Thor integration was approved then delayed and modified since when exactly?? True, the agents employed to delay and kill dash are working hard.


There is also a POSE issue with v17 that won't be addressed until v18 now, that seems like something that should have
been addressed with a minor release and not rolled into v18.
 
There is also a POSE issue with v17 that won't be addressed until v18 now, that seems like something that should have
been addressed with a minor release and not rolled into v18.

VLzXVKc.jpg


Source : www.reddit.com/r/dashpay/comments/vzkdce/dash_platform_sprint_86_review_summary/

+

zB6iUat.jpg


Source : https://www.dashcentral.org/p/DCG-Sup-Fund-July22#comments

It does not seem to be an issue after all. Hopefully they activate the hard fork today or in the next few days on Testnet and then pick a launch date for v18 on Mainnet. The number of release candidates (9 release candidates for v18 so far) is still on the high side though. Something that happened with previous major updates as well and which devs supposedly would work on.... to cut that short. It is back in force with v18.
 
Last edited:
VLzXVKc.jpg


Source : www.reddit.com/r/dashpay/comments/vzkdce/dash_platform_sprint_86_review_summary/

+

zB6iUat.jpg


Source : https://www.dashcentral.org/p/DCG-Sup-Fund-July22#comments

It does not seem to be an issue after all. Hopefully they activate the hard fork today or in the next few days on Testnet and then pick a launch date for v18 on Mainnet. The number of release candidates (9 release candidates for v18 so far) is still on the high side though. Something that happened with previous major updates as well and which devs supposedly would work on.... to cut that short. It is back in force with v18.


That is not the issue I am talking about. @xkcd has been monitoring this issue on V17 mainnet, it's a separate issue that won't
be addressed with a minior release but will be bundled into v18. There are rolling POSE bans that have taken out mainnet nodes
that we have to wait on v18 now to fix.
 
And by coincidence, the Thor integration was approved then delayed and modified since when exactly?? True, the agents employed to delay and kill dash are working hard.

Mostly the old members (and the numerous dead/inactive) understand this truth, because they have seen a lot of things happening around. Most of the new members dont believe in this scenario. For the newbies there are no agents at all, and the ignorance of the newbies makes the agents very happy and feeds them.
 
Last edited:
In order to understand this truth you have to be a very old member. New members dont believe in this scenario. For the newbies there are no agents at all, and the ignorance of the newbies makes the agents very happy.

There are no more agents in DCG, we got rid of them all. DCG is now mostly just a large group of developers and they are getting a lot of work done, just watch the github repos and you will see a lot of activity there. v18 will be released to mainnet in August and the process to fork in the reduced proposal fee will start soon after. It's been a long wait, but I think it will be worth it, we are getting a lot of features that make Dash better.
 
There are no more agents in DCG, we got rid of them all. DCG is now mostly just a large group of developers and they are getting a lot of work done, just watch the github repos and you will see a lot of activity there.

The DCG is funded by the masternodes. It is difficult for me to believe that among the masternode voters there are no government agents. These agents will always vote for a DCG compatible to the agents' guidelines, or at least for a DCG that is neutral and does not threaten the agents' red lines.

A possible remedy of the above (in case we want to confront the agents of course because some ordinary people that are not agents may dont want to confront them) is the proof of individuality. Because the agents may have a lot of money, may have a lot of votes, but they are not numerous , so their individuality can be spotted by their votes and by their sponsorships. When a bad actor is spotted as an individual, then the community can diminish his voting power.

v18 will be released to mainnet in August and the process to fork in the reduced proposal fee will start soon after. It's been a long wait, but I think it will be worth it, we are getting a lot of features that make Dash better.
I hope your prediction to become a reality.
 
Last edited:
The DCG is funded by the masternodes. It is difficult for me to believe that among the masternode voters there are no government agents. These agents will always vote for a DCG compatible to the agents' guidelines, or at least for a DCG that is neutral and does not threaten the agents' red lines.

A possible remedy of the above (in case we want to confront the agents of course because some ordinary people that are not agents may dont want to confront them) is the proof of individuality. Because the agents may have a lot of money, may have a lot of votes, but they are not numerous , so their individuality can be spotted by their votes and by their sponsorships. When a bad actor is spotted as an individual, then the community can diminish his voting power.


I hope your prediction to become a reality.

You are right, it is possible some agents hide in the MNO group, their votes should reveal themselves though.
 
You are right, it is possible some agents hide in the MNO group, their votes should reveal themselves though.

What really reveals the agents (or the agents' proponents) is some crucial government decisions.
Thats why the agents do not want government decisions to be asked into the dash budget system.
Fortunately, with the upcoming reduction of the proposal fee, more government decisions will be asked into the budget, and thus the agents will be revealed.
 
Last edited:
So the reduction of the proposal fee was decided to 1 dash, after 1 year it was finally implemented , since then the dash price currently reaches the botton, but stil we have no proposals in the budget. This situation reveals and proves the huge wrong of those who were arguing and constantly voting against the reduction of the fee all these 7 years. Will one day these persons be judged for their vote?

Although the fee is now reduced to 1 dash, no spam proposals appeared yet in the budget, so the logical thing is to reduce the proposal fee even more. Obvioulsy, and as long as we still have no proposals in the budget, reducing the proposal to 1 dash was proved to be the wrong decision. We have to reduce the proposal fee even more.

Adaptive proposal fees are ugently needed.

Proposal: Adaptive Proposal Fees | Dash Forum
 
Last edited:
True, where are all those that said we'd be flooded?

They were proved filthy liars, and should be punished not for what they said, but for what they voted.

Unfortunately no punishment is yet implemented for those who vote unwisely. At least, and thanks to the dashninja,pl archives that date back in 2017 (mnowatch's ancient reports are also available), we know the masternodes who voted against...
Proposal "Reduce_proposal_fees_to_dot1_DASH" - DashCentral.org -- 257 Yes / 904 No / 52 Abstain --> If the report of DASH Ninja is accurate, are 419 no_voters still among us!!!!????
Proposal "REDUCE_PROPOSAL_FEES_TO_1_DASH" - DashCentral.org -- 790 Yes / 719 No / 13 Abstain -> if the report of DASH Ninja is accurate, are 406 no_voters still among us !!!???
Proposal "Adaptive-Proposal-Fees" - DashCentral.org --- 458 Yes / 393 No / 74 Abstain ---> if the report of DASH Ninja is accurate, are 212 no_voters still among us!!!????
The creator of dashninja, @elbereth (last seen May 17, 2022), could help us answer the above 3 questions.

But then I wouldn't say it is too expensive, just that no one knows or cares anymore.
Thats why the proposal fee should be reduced even more, in order to incentivize people to propose. It should be reduced until the spam appears, then increased again to prevent spam's flood.

Adaptive proposal fees are urgently needed.
Proposal: Adaptive Proposal Fees | Dash Forum
 
Last edited:
Yeah, good observation! I think the people that were upset about lowering the proposal fee just wanted to hold Dash back and make it an elitist coin, not sure, maybe they were just stupid.

Given the price of $40 however, I don't support lowering the fee any more, maybe we can consider it when the Dash price is back over $400. One of the benefits of the lower proposal fee is that we are burning less Dash from the DAO, so the Dash goes further whereas before POs would request the Dash they need + 5 Dash reimbursement, that was waste, we are 5x more efficient now.

Final note, you now have the ability to create a proposal in minutes at https://mnowatch.org/proposal-generator/ the advantage of this one is additional validation compared to the DCG one, better uptime and streamlined flow, try it today!
 
Given the price of $40 however, I don't support lowering the fee any more, maybe we can consider it when the Dash price is back over $400. One of the benefits of the lower proposal fee is that we are burning less Dash from the DAO, so the Dash goes further whereas before POs would request the Dash they need + 5 Dash reimbursement, that was waste, we are 5x more efficient now.

We have to wait a little more, for a couple of months, and if the budget system still remains empty of proposals, a further reduction of the proposal fee should be the only way to go. The important thing is to create a mechanism where the fee not only could be reduced, but also increased, as adaptive proposal fees suggests.
 
Last edited:
Back
Top