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. 
Reduce the proposal fee to one dash
- Thread starter xkcd
- Start date
MNOwatch - VoteHashGroups 2021-07-12-00-52-24
Last edited:
MNOwatch - VoteHashGroups 2021-07-12-00-52-24
mnowatch.org
Among the 10 individuals who vote NO, only 2 have a decent vote history (1435 and 457). All the rest have no significant history.
The first individual that appears in the table, a 16whale, has a vote history as a group of only 4 reports. You can see all the votes of this 16whale here.
Having small history means that, either all the individuals are newbies, or people are trying to hide their individuality. If you look at the date of their first transaction, it is probably the second case. Anonymity culture in Dash stands, and thats good!
For Dash to win the current world monetary system, anonymity is the number one priority.
Last edited:
I mean, you could almost put names to those groups. Almost....
I'm just going to throw some ideas out there related to this topic:
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.
@xkcd good luck with your proposal.
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.
@xkcd good luck with your proposal.
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.
Thanks!
Right! .. Makes sense... It's nice to know it will be improved.. This could have major impact...
An 111whale voted in favor of the proposal.
mnowatch.org
The whale is a 2017 generation, the oldest transaction of this whale dates back in 2017.02.26
The oldest masternode of this whale is 014fb8ab3baf443834a6301d4d9e954aa6710a4fdbab801be8226902d1855b43-1
it appears in this report https://mnowatch.org/the_results_dashd_01-07-52-07-01-2019.html
The oldest voting masternode of this whale is 3e8cecd6da955442105c68c1b13f374d27de0badf793fef0404c9b5efec12f62-0
The votes appear in this report https://mnowatch.org/the_results_da...849546421195671962169980487098946461442830820 . The 24whale back then, casts a single vote in favor of https://www.dashcentral.org/p/DashCrypto-Team-Comp-Supporting-Funds
The oldest IP of the whale is 193.29.57.61. It appears in https://mnowatch.org/the_results_dashd_2020-01-12-00-52-42.html
The oldest voting IP of the whale is 173.254.204.80 and appears in https://mnowatch.org/the_results_da...609122908226971519850757092395581960755896595
Maybe I will code a public mnowatch query for all the above, someday.
MNOwatch - Diff 2021-07-19-13-02-26
The whale is a 2017 generation, the oldest transaction of this whale dates back in 2017.02.26
The oldest masternode of this whale is 014fb8ab3baf443834a6301d4d9e954aa6710a4fdbab801be8226902d1855b43-1
it appears in this report https://mnowatch.org/the_results_dashd_01-07-52-07-01-2019.html
The oldest voting masternode of this whale is 3e8cecd6da955442105c68c1b13f374d27de0badf793fef0404c9b5efec12f62-0
The votes appear in this report https://mnowatch.org/the_results_da...849546421195671962169980487098946461442830820 . The 24whale back then, casts a single vote in favor of https://www.dashcentral.org/p/DashCrypto-Team-Comp-Supporting-Funds
The oldest IP of the whale is 193.29.57.61. It appears in https://mnowatch.org/the_results_dashd_2020-01-12-00-52-42.html
The oldest voting IP of the whale is 173.254.204.80 and appears in https://mnowatch.org/the_results_da...609122908226971519850757092395581960755896595
Maybe I will code a public mnowatch query for all the above, someday.
Last edited:
Maybe the 111whale existed prior but on different IPs? I mean, can't be that many with approximately 111 mns.
Back in 2020-7-17 he had 24 voting masternodes https://mnowatch.org/the_results_da...609122908226971519850757092395581960755896595
Probably he/she bought more masternodes.
When a whale increases or decreases his fleet, it gets a new hashgroup ID, so we cannot spot it by the hashgroup ID but only by the way he/she votes.
And some other info. The oldest collateral address of this 111whale is https://bitinfocharts.com/dash/address/Xaxb8MzfVzvoVUVLnQSGdY9hkUWU9ZBWfF and appears in https://mnowatch.org/the_results_dashd_2019-08-16-11-00-55.html
This collateral address, back in 2019-8-16, used to have IP 89.46.79.249 from Rome-Italy. But now this IP changed and the collateral address has IP https://ipinfo.io/69.61.107.252
[email protected] , is it you ?
In a post somewhere here in this forum, I have predicted your come back after the end of the 24months-"vote the numbers" dashcrypto proposals. Did my prediction come truth? Or is this 111whale @Pasta related?The 111whale looks also very similar to this 102whale --> https://mnowatch.org/the_results_da...717162377579737610377454715722627209905374208 because of the 69.61.107.* IP range
Last edited:
I suppose this is my Waterloo. I will have to take down the one last masternode I was keeping as a souvenir if this passes. It was all I could stand having to read about the fictional accomplishments of DashRetail and DashPress. Next up is Joel's Incubator Initiative and God knows what other SCHNORRERS are waiting in the wings with their pitches. I can't do it.
GOODBYE, CRUEL DAO!
GOODBYE, CRUEL DAO!
I just want to say thank you to everyone that help make this happen. I think this is a very positive step.
I do too and thanks for your support GrandMasterDash, we couldn't have done it without you!
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!!!!)
Last edited:
THE RECUCTION TO 1 DASH WAS DECIDED JULY 2021!!!!
THE CODE WAS READY SINCE THEN!
AND NOW WE HAVE MAR 2022 AND STILL NOTHING!!!!!!!
WHAT THE HELL THE DASHCORE GROUP IS DOING??????????????????????????
HOW MUCH MORE PATHETIC THE Dash Core Group COULD BE????
By the way, look at the proposals of Cardano (and compare it to the proposals of dash), to understand how the budget of a vivid (and of a dying) crypto looks like.
Last edited:
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)
Tags classify the proposals and inform/facilitate the voters in order to vote more wisely and more accurately. Tags are a good start for a decision tree similar to the knowledge tree to grow up.
I asked for Tags to be implemented 5 years ago, but once again the pathetic timocracy of masternodes and the pathetic DCG ignored it.
Last edited:
THE RECUCTION OF THE PROPOSAL FEE TO 1 DASH WAS DECIDED JULY 2021!!!!
THE CODE WAS READY SINCE THEN! AND NOW WE HAVE ALMOST AUGUST 2022 AND STILL NOTHING!!!!!!!
This is a great anniversary!
My deep respect to the agents for the superb job they are doing that keeps the dash community dead.
GO, GO, AGENTS! DO YOUR WORK! KEEP THE RED LINES UNTOUCHABLES.
AND ABOVE ALL, BEWARE, NOBODY IN THE UNIVERSE SHOULD BE ALLOWED TO VOTE THE NUMBERS !!!
"And the Raven, never flitting, still is sitting, still is sitting. On the pallid bust of Pallas just above my chamber door;
And his eyes have all the seeming of a demon’s that is dreaming,
And the lamp-light o’er him streaming throws his shadow on the floor;
And my soul from out that shadow that lies floating on the floor
Shall be lifted—nevermore! "
When accountability?
Last edited:
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.
Last edited:
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.
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:
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.
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.
Last edited:
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.
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.
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:
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.