Hi Everybody, this proposal is up now https://www.dashcentral.org/p/reduce-the-proposal-fee-to-one-dash looking forward to comments and votes for this one.
|Number of Masternodes||HISTORY OF THIS IP GROUP / HASH OF THE GROUP||IP_ADDRESSES||FIRST_TRANSACTION|
|0016||(History=0004) 908080388744148790594174729084418870147507627030||188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168||2017.03.18.01.09.51|
|0004||(History=0014) 1004001410982918210387359274792507611769346451469||22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206||2015.01.24.10.23.02|
|0002||(History=0005) 495732815981492340682911690189512927693168185580||220.127.116.11 18.104.22.168||2015.08.06.23.59.32|
|0002||(History=0457) 424475809895317093345188976283558829094804707143||22.214.171.124 126.96.36.199||2019.02.06.00.19.21|
|0002||(History=1435) 287630872607453305926279321519584598903508316540||188.8.131.52 184.108.40.206||2018.09.29.14.36.49|
Number of Masternodes HISTORY OF THIS IP GROUP / HASH OF THE GROUP IP_ADDRESSES FIRST_TRANSACTION 0016 (History=0004) 908080388744148790594174729084418870147507627030 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 2017.03.18.01.09.51 0004 (History=0014) 1004001410982918210387359274792507611769346451469 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 2015.01.24.10.23.02 0002 (History=0005) 495732815981492340682911690189512927693168185580 22.214.171.124 126.96.36.199 2015.08.06.23.59.32 0002 (History=0457) 424475809895317093345188976283558829094804707143 188.8.131.52 184.108.40.206 2019.02.06.00.19.21 0002 (History=1435) 287630872607453305926279321519584598903508316540 220.127.116.11 18.104.22.168 2018.09.29.14.36.49 0001 (History=0115) 712553330797741417728822608835861182963673204545 22.214.171.124 2017.08.04.17.37.58 0001 (History=0143) 634901643833882751210658684266034302363282753598 126.96.36.199 2017.03.22.21.18.25 0001 (History=0146) 312325744922778793525989474094021920171952404664 188.8.131.52 2017.07.31.04.14.56 0001 (History=0133) 1320405264515327066165573448394951852214149450698 184.108.40.206 2015.11.02.23.40.15 0001 (History=0121) 1241299303178228121842056282581817422295000452958 220.127.116.11 2017.12.23.04.03.33
Yes, there are an infinite number of ways to make the system more reflexive, but the constraint we had to work with was this has to be a simple change, this is because at some date in the future a bigger overhaul of the governance system needs to be done and we don't want to tie up devs working on something that will be replaced soon and we don't want to tie up devs working on this change while evo is still not out the door, as such, it was either make this simple change or nothing at all.There could be a range fee starting from a certain amount of dash and topping it up as well. Projects who want more priority pay more and the ones who don't or can't have less priority. Also, if the proposal is not considered spam or is accepted, a percentage of the proposal fee could be refunded.
Thanks!@xkcd good luck with your proposal.
Back in 2020-7-17 he had 24 voting masternodes https://mnowatch.org/the_results_da...609122908226971519850757092395581960755896595Maybe the 111whale existed prior but on different IPs? I mean, can't be that many with approximately 111 mns.
Anyone knows when the 1 dash proposal fee will be implemented?I do too and thanks for your support GrandMasterDash, we couldn't have done it without you!
THE RECUCTION TO 1 DASH WAS DECIDED JULY 2021!!!!Anyone knows when the 1 dash proposal fee will be implemented?
yes votes --> MNOwatch - VoteHashGroups 2021-07-25-16-30-32
no votes --> MNOwatch - VoteHashGroups 2021-07-25-16-30-32
THE PROPOSAL WAS DECIDED JULY 2021 AND NOW WE HAVE JAN 2022!!!!!!!
WHAT THE HELL THE DASHCORE GROUP IS DOING??????????????????????????
(by the way, look at the 6th coin's governance page. Dash used to be the 6th coin, but due to the stupid decisions of the masternodes and due to delays of the DCG it hardly remains now the 90th coin!!!! Such a shame!!!!)
And also look , cardano's proposals are tagged!!! (the current cardano tags are: Developer, Dapp&intergration, Distributed Decision making, proposer outreach, catalyst value onboarding, metadata, grow cardano, grow africa, scale up cardano defi, cardano emerging threat alarm, multilangual resources, defi & microlending africa, dlt enterpeneur toolbox, partnership for global adoption, nft buisness models, atala prism mass scale adoption, disaster when all is at stake, cardano community hubs, improve and grow auditability, fund7 challenge setting, sponsored by leftovers)
THE RECUCTION OF THE PROPOSAL FEE TO 1 DASH WAS DECIDED JULY 2021!!!!THE RECUCTION OF THE PROPOSAL FEE TO 1 DASH WAS DECIDED JULY 2021!!!!
THE CODE WAS READY SINCE THEN!
AND NOW WE HAVE MAR 2022 AND STILL NOTHING!!!!!!!
Why are you trying to find excuses for the agents?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.
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.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.
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.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).
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?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.
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.
Source : www.reddit.com/r/dashpay/comments/vzkdce/dash_platform_sprint_86_review_summary/
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.
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.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 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.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.