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

I think Dash needs some changes

Still so much zealous support for devs that till this date still not have produced a feature-complete Platform on Testnet, are still introducing Platform Github feat. pull requests that have little to do the last remaining open feature Masternode Voting (making it doubtfull that Masternode Voting really is the last Platform feature to implement, before a code freeze). Which means we could be in this Platform not-feature-complete state for quite some time.

Devs who made countless promises to release Platform to Mainnet end 2022, end 2023 and now somewhere 2024 under their 'completely new team and new leadership', made the Dash Roadmap an embarrassment instead of an asset by constantly moving goalposts forward or removing them completely, caused a bloody chain halt on Mainnet, caused so many crashes / downtime of Testnet these last few years that i lost count, abandoned Testnet testing on dash.org/forum, to this day continue making unreliable project delivery estimates, can not even communicate to MNO's or the Dash community with which Core version Platform should activate on Mainnet, show zero results at actually improving their project delivery estimates and have shown to be late / too late when it comes to responding to changing market conditions, leading to a situation where those devs were basically out of funding during this bear market. Which they solved by asking and getting an increase of DAO budget and asking for more compensation, while still introducing additional budget funding requests which look to be an ongoing process, despite earlier statements that this was just for a few months (3 months ?).

The only thing i am looking forward to is the increase of APY that Evonodes will receive, once devs finally merge the mn_rr hard fork in some Core version, which will activate the Platform features. But if that happens during a Dash bull market / bullrun, then that increase of APY will be weighted against my need to this time take more profit during that (usually short) Dash bull market and the inevitable Dash bear market that follows. Unless devs manage to restore some of my lost trust in them by giving reliable project delivery estimates going forward and start providing a reliable and informative Dash Roadmap. But so far i have not noticed any signs of that.

From a project management point of view, this all has been a disaster for many many years now (even before the new team / new leadership), with one steady fixed outcome : delay & increased uncertainty.

#end_of_rant


Yes, qwizzie, the same team that re-wrote the antiquated platform from JavaScript to Rust, the team that threw out MongoDB and invented a new Database system called GroveDB https://www.grovedb.org/ the same team that linked AI into the generation of data contracts with https://dashpay.io/ the same team that brought us Quorum Rotations, updated the BLS schema, introduced HD wallets by default, refactored Sentinel into DashCore and much much more. Platform is now looking like a viable product, we have an explorer for it, we have an SDK for it, we have numerous dapps already developed for it and yes, we are closer than ever to a mainnet release.

I would put it back on you and the OP, do you really believe that the best thing for this project now is to fire the only devs we have? Do you think the muppets I listed above if reinstated could do a better job than the current team? Or are you just venting your valid and concerning frustrations?

I think all of us wish that things were moving along faster than they have been, but we've been following along with the story and we can see the PRs into Github, it just is a very big job and compared to other projects, we really don't have a big team to get things done, again, let's thank the previous administration for burning our resources and landing us here. I am interested to know in your solutions, Qwizzie. It is easy to stamp our feet and say fuck those devs! But even if we did, have you seen the calibre of people seeking employment with DCG? There are probably only a handful of people the world over capable enough to deliver this project, it's not as simple as webpage and that's kind of a good thing too, because it means the tech will stay with Dash even after release and thus we will retain or lead in market share.
 
I would put it back on you and the OP, do you really believe that the best thing for this project now is to fire the only devs we have? Do you think the muppets I listed above if reinstated could do a better job than the current team? Or are you just venting your valid and concerning frustrations?
Where did i mention i want to fire devs ? Lets just stick to what i actually wrote in that post.

What i want is simple : clarity to Dash users / Evonode owners / Masternode owners about which Dash Core version will activate the Platform features, a stop to the endless delays coming from the Platform teams and Platform needs to get feature-complete and put into code freeze on Testnet, where only bug fixes can be merged. And a reliable public Dash Roadmap needs to be put into place, a basic necessity.

This all is long long overdue and falls under Sam's responsebility.

Wake me up when this is done.
 
Last edited:
Where did i mention i want to fire devs ? Lets just stick to what i actually wrote in that post.

What i want is simple : clarity to Dash users / Evonode owners / Masternode owners about which Dash Core version will activate the Platform features, a stop to the endless delays coming from the Platform teams and Platform needs to get feature-complete and put into code freeze on Testnet, where only bug fixes can be merged. And a reliable public Dash Roadmap needs to be put into place, a basic necessity.

This all is long long overdue and falls under Sam's responsebility.

Wake me up when this is done.

Qwizzie, these are valid questions and you can address them to the team during today's sprint review, please tune in and ask them clearly and hopefully you get some answers.

I did already inquire about the MN_RR EHF and the answer is that v20 can still activate platform, if it were ready to ship today. We will need a v21 if there are breaking changes in Platform that also require a new version of the Dash L1 protocol. I hope that helps.
 
The only thing that will change the status quo of poor results is more no votes for DCG and other ineffective POs.

The small group of voting MNOs have proven their unwillingness to hold DCG and other POs accountable for lack of results.

We need to get more MNOs to pay attention to governance and demand better results. The only way to do that is to make it worth their time.

Give all remaining funds at the end of each cycle to the MNOs, causing a shift in perspective. Instead of seeing the treasury as free money to be handed out, they will see it as their money, and will be more careful with it. Watch as they begin to participate, ask questions, and start to vote no, ending the easy money for all the ineffective POs. It will also slightly improve MN ROI.

This is *the* key missing piece of the incentive structure. Somehow the community still has not understood and accepted this.
 
The only thing that will change the status quo of poor results is more no votes for DCG and other ineffective POs.

Defunding core will not get Evo delivered sooner, instead it will kill the project and cause mass panic selling.
 
Platform releases are temporary crutches, but in the long term, DASH is a zombie, neither alive nor dead, uninteresting and cheap.
Limit the coin supply to 12 222 222, this will increase the value!
Digit is beautiful and raises questions and interest.
The magic number will save the project!
This is the only way out of the terrible state of affairs and we can count on $500 and perhaps even 0.01 BTC for 1 DASH
 
Last edited:
Because Dash is such a well established and viable cryptocurrency, it is considered a coin that is here to stay. I sometimes thinks like you and the above person said. I need to discuss it more because of its future price.
 
Defunding core will not get Evo delivered sooner, instead it will kill the project and cause mass panic selling.

I think a little exaggerated. How could it possibly lead to mass panic selling when many here believe - and underscored by the dash.org website - that dash is "digital cash"?

The Dash Platform primary function has nothing to do with "digital cash". Not delivering on a secondary unrelated function doesn't seem so disastrous to me.

Projects like Thorchain are more cash related than Dash Platform.

The logic is simple, to me at least. If Dash Platform really is so necessary and centric to dash's future, then the "digital cash" message and identity is completely wrong. Providing storage related tools doesn't make the chain token "digital cash", for if it did, then RUNE is also digital cash.
 
Defunding core will not get Evo delivered sooner, instead it will kill the project and cause mass panic selling.
Defunding DCG will cause the separation of the DCG departments.
Thus, in the next budget, the pure core will be voted again, while Platform and all the rest unnecessary DCG departments will be rejected.

So defunding DCG for a month is a very good idea.

SEPARATE THE WHEAT FROM THE CHAF, NOW......





......and vote the Numbers! (also vote for Encointer, the real EVO)
 
Last edited:
Defunding DCG will cause the separation of the DCG departments.
Thus, in the next budget, the pure core will be voted again, while Platform and all the rest unnecessary DCG departments will be rejected.

So defunding DCG for a month is a very good idea.

SEPARATE THE WHEAT FROM THE CHAF, NOW......





......and vote the Numbers! (also vote for Encointer, the real EVO)

Yep, I think this would happen too.
 
Yep, I think this would happen too.
So are you finally starting to see why more MNOs participating would be a good thing? Your fear of this change is puzzling, given your enthusiastic support of far, far more drastic changes. Get on board. Help the community put in the missing piece. Watch us finally get results from the treasury!!
 
So are you finally starting to see why more MNOs participating would be a good thing? Your fear of this change is puzzling, given your enthusiastic support of far, far more drastic changes. Get on board. Help the community put in the missing piece. Watch us finally get results from the treasury!!

So are you finally starting to see why more MNOs participating would be a good thing?

This a bit harsh. I've always been a supporter or more people voting in the DAO and I am supporter of the MNO plan where the DAO is funded from the MNO pay directly and exclusively.

What I objected to above, is defunded the DCG proposal. I did agree what if it were defunded and splinter team of Core and Mobile would emerge to request direct funding. Even so, given that Platform is close to readiness (did you watch the sprint review?) I think we should support to the end and see the product finished and deployed to mainnet. What I don't like is the platform team cannabalising Pasta and Ody to work for them and neglecting Core. That is a dog act and if it keeps up, it could be something that would cause me to pull the pin on my DCG support.
 
This a bit harsh. I've always been a supporter or more people voting in the DAO and I am supporter of the MNO plan where the DAO is funded from the MNO pay directly and exclusively.

What I objected to above, is defunded the DCG proposal. I did agree what if it were defunded and splinter team of Core and Mobile would emerge to request direct funding. Even so, given that Platform is close to readiness (did you watch the sprint review?) I think we should support to the end and see the product finished and deployed to mainnet. What I don't like is the platform team cannabalising Pasta and Ody to work for them and neglecting Core. That is a dog act and if it keeps up, it could be something that would cause me to pull the pin on my DCG support.

Incentives matter. That is a fundamental point to why MNs exist, and something that was well-understood by the Dash community. "Skin in the game" is another one.

Where is the incentive for DCG and other proposal owners to do better, or to be more responsive to the community, when they know they will probably be funded over and over?

Really think about that.

The majority of MNOs don't participate in governance. We must directly incentivize them to participate and vote. Give them the leftover funds at the end of each cycle. They will come.


They will bring questions and ideas with them. Their participation will put good, positive pressure on proposal owners, which will cause POs to be more responsive and effective, to the benefit of the entire project.

What is so hard to understand about this? How does this community still not get it?

When will you, who clearly has time to do so, help popularize this simple, clear, missing piece of the puzzle?

Dash will benefit from this change. This needs to happen. Evo alone will not save Dash.

Shout this from your megaphone. Help me help this dying community!

You, quizzie and the other OGs ought to be ashamed of yourselves and only have yourselves to blame for the current state of things for not getting this through your heads and helping me with this.
 
The majority of the incoming funds may be illegally gained, but not also necessarily immorally gained. On the other hand the law that defines what is legal and what is illegal, has been decided by using immoral election methods.

And this applies to almost all governments worldwide, including Dash's government. Because over here the Dash laws have also been decided by a perpetually immoral DCG cabal (aligned to a masternode whales cabal) which cunningly and immoraly refuses/avoids to set the Dash status quo under vote (by using a moral election method of course).

Dash DAO goes from bad to worse.

When the Dash Status Quo will be questioned?
 
@vazaki3

Most likely when you stop talking to yourself.

I take it that you are still a bit upset about your budget proposal (https://www.dashcentral.org/p/ENCOINTER-SUPPLEMENTAL-MAR24) not passing ? Smart decision of those MNO's that participated and a clear signal from those MNO's that did not participate, indicating (at least to me) that the topic was apparently not interesting enough to vote on.

Also interesting that the mass opvoting of this budget proposal (+16) through an arsenal of DC accounts, had very little effect on the outcome.
I guess the Dash DAO has matured enough for MNO's to see right through that DC exploit tactic.
 
Last edited:
@vazaki3

Most likely when you stop talking to yourself.

I take it that you are still a bit upset about your budget proposal (https://www.dashcentral.org/p/ENCOINTER-SUPPLEMENTAL-MAR24) not passing ? Smart decision of those MNO's that participated and a clear signal from those MNO's that did not participate, indicating (at least to me) that the topic was apparently not interesting enough to vote on.

The majority of the MNOs is not interested in changing the stupid status quo that was set by "god" Evan a long time ago. Thats why Dash is dying, and it will die even more.

I am not upset at all. I have no masternode, I have just 2 dash in my wallet, so I dont care. And if my proposal passed, I would have a lot of unpaid work to do, if I wanted to appear consistent to myself and to what I promissed. Fortunately my proposal didnt pass, so I stay calm, I have no work to do, so I just sit and watch your upcoming death (which is certain).

And I dont care at all for your upcoming death. But you should care. Because (in case of course you are not a government agent financed to destroy dash) you are the one who have invested 8000 dash in this dash stupidity and you are the one who will lose your money.

@qwizzie. Unfortunately your poor soul is fully possessed by daemons. You are going straight to death, and the daemons make you feel happy about it.
 
Last edited:
Current DCG todo list before releasing Dash Platform to Mainnet :

Consensus issues discovered:
Making sure that replaying state transitions can not take down the network (2 people for 4 days left of work - most work here already completed) Done
Implement multithread drive query solution (discovered during stress tests) (3 people for 2 weeks left of work) Done
Ask for all core information once for all state transitions in a block (discovered during stress tests) (2 people 3 days)
Bug in data contract queries (1 person 1 day) Done
Bug in race condition between query threads and main consensus threads (1 person 2 day New) Done
Data contract validation fixes (1 person 3 days - discovered during review) Done
Move multiple state transition validation components from mempool validation to consensus validation(1 person 5 days) Done
Found a replay attack on identity create (1 person 3 days) Done

Features left:
Masternode Voting (2 people for 7 days 4 days left of work - currently in progress)

Fine tuning
Verifying all state transitions against potential attacks (2 weeks 2 people) Initial work Done
Making sure that fees are set to values that represent costs to actual Evonode operators (3 weeks 2 people)
Internal code review (All the team 2 weeks)

SDK
Making sure that clients have properly integrated the Dash SDK (3 man/weeks left of work - mostly taken on by mobile team) Done (This task only represented the Dash SDK integration part - Mobile features will take longer)

Testing
Additional stress tests (2 people 1 week) Initial work Done (might have another round of stress tests right before release)
Additional mechanisms for better testing (1 person 3 weeks - in progress - 1 week left)
Final testing of protocol upgrades (2 people 3 days)
Chain halt mitigation process (2 people 3 days)

Might be needed
State Sync (2 people 4 weeks - in progress - 2 weeks left) - We hope to be able to release without this, however Core Team is helping on this.
Query fees (2 people 2 weeks) - We currently do not charge state transitions for lookup queries, since this is vastly inferior to other state transition costs we believe we can release without this feature. Not needed for release.
Dapi rewritten in Rust (2 people 3 weeks) - Dapi is currently written in Javascript, it's only 14k lines of code (which is mostly boilerplate). Since it was never an expensive part of the system this was kept in Javascript, however it might prove too unreliable. Currently though we see it working well enough for release. We strongly no longer believe this is needed for release.

Dash Roadmap :

Knipsel.JPG


Knipsel.JPG

Source : https://github.com/dashpay/platform/pull/1829 (basic NFT support)

Why is Sam working right now on NFT support, when that feature is scheduled for Dash Platform v2.0 ?
Why is Sam not fully concentrating his time on finishing the last remaining consensus issue, Masternode Voting, verifying Platform fees and continuing work on internal code review ? How will Dash Platform ever get feaure-complete on Testnet for MVP release on Mainnet, when features like these are just thrown into the mix ?

Knipsel.JPG

Source : https://www.dashcentral.org/p/DCG-SUPPLEMENTAL-APR24#comments

Sam's answer unfortunetely makes sense now, seeing how much time he is spending on features not even on DCG immediate todo list. Features like NFT support.
 
Last edited:
Back
Top