Proposal “DCG-SUPPLEMENTAL-MAR24“ (Completed)Back

Title:Dash Core Group March Supplemental Funding Proposal
Owner:quantumexplorer
One-time payment: 834 DASH (24184 USD)
Completed payments: 1 totaling in 834 DASH (0 month remaining)
Payment start/end: 2024-03-10 / 2024-04-09 (added on 2024-03-16)
Votes: 526 Yes / 86 No / 0 Abstain

Proposal description

What does this specific proposal fund?

DCG reserves are slowly getting better but are still low, this proposal aims to speed up recovery of a small buffer, so DCG can be in a more healthy position sooner.

How are things?

February, like January was a very productive month. One of the main massive achievements was that we were able to split platform into 3 threads, so that querying and mempool validation could not disrupt the blockchain from advancing through consensus. High on this achievement 

What is left to do for Evolution/Dash Platform to be released?

We have work pretty much divided into many categories of work. Please understand the time required here are estimates. The work added here is also what we currently know of, and as testing is a dynamic process things might be added to this list as they are discovered. Also please note that some tasks can only be done by certain individuals on the team. Some team members are assigned to lower priority tasks because they are best suited to take on such tasks since putting them on the more complicated tasks would not give good results.

This is also a high level overview of the major items, there are many much smaller items that we are not mentioning here. You can see all the work being done here: https://github.com/dashpay/platform/pulls?q=is%3Apr+is%3Aclosed (and this only the Platform side - not tenderdash, grovedb or the platform client text user interface that you can find in other projects on our github)

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 - in progress) Done

Features left:
Masternode Voting (2 people for 7 days left of work - currently postponed till after issues are finished)

Fine tuning
Verifying all state transitions against potential attacks (2 weeks 2 people - New - in progress)
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)

Client side
Making sure that clients have properly integrated the Dash SDK (3 man/weeks left of work - mostly taken on by mobile team)

Testing
Additional stress tests (2 people 1 week)
Additional mechanisms for better testing (1 person 3 weeks - in progress)
Final testing of protocol upgrades (2 people 3 days)
Chain halt mitigation process (2 people 3 days)

Might be needed
State Sync (2 people 3 weeks - in progress) - 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.
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.

Did DCG start hiring again?

We sadly had a departure in the GroveDB team and are looking to backfill that position. Right now that is the only hire we are looking to do, at least for the next 2 or so months.

How much of an impact do the supplemental proposals have?

A big impact. The supplemental proposals will aid our recovery and put us in a better position for growth sooner.

If you have any questions, please direct them to quantumexplorer at dashcentral.

Requested funding is as follows for the March 25th superblock:
  • 833 Dash ($29,571.5 USD @ $35.5 per Dash)
  •     1 Dash Proposal fee reimbursement
Total: 834  Dash

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
1 point,4 months ago
Devs have a terminal user interface developed (TUI) to stress test Platform for themselves.

Is there some kind of TUI in development for Evonode owners and Dash users with regards to Platform Credits (converting to & withdrawing from) ? To me that seems like a missing feature that needs to be developed and tested thoroughly, to prevent possible exploitation or bugs and should not be handled as an afterthought.
Reply
2 points,4 months ago
> Devs have a terminal user interface developed (TUI) to stress test Platform for themselves.

No, it is on github and anyone can run it and try to attack Platform with it. The testing you suggest can be done by the community now that testnet is back online.
Reply
1 point,4 months ago
Whatever.... i just want to know if a terminal user interface is getting developed by DCG that gives Evonode owners and Dash users insight in how much Platform Credits are stored for them on the Platform chain and provide them with direct control over those Platform Credits (allowing them to withdrawal those Platform Credits to dash).

Such feature should have been developed after they finished coding withdrawals and should be part of the stress test. I suspect it is still missing...
Reply
2 points,4 months ago
It's a good idea. Should be like a day of work.
Reply
2 points,4 months ago
Thank you.
Reply
-3 points,4 months ago
quantumexplorer.
Platform issuance is temporary crutches, and in the long run DASH is a zombie, neither alive nor dead, uninteresting and cheap.
Limit issuance to 12 222 222, otherwise you won't have the entire budget to eat and compensation won't help you!
The above number is beautiful and raises questions and interest.

The number 2 is a symbol of balance, prosperity, teamwork, peace and harmony. The number 2 also has a positive vibrational energy associated with service and openness, but at its core the number 2 represents partnerships.

The magic number will save the project!
Reply
4 points,4 months ago
No, but you are free to make a proposal to the network.
Reply
-3 points,4 months ago
Large masternodes have organized themselves into a group and vote unanimously, everyone has known this for a long time. Centralized voting for selfish purposes, which destroys DASH, so I don't see the point in creating a proposal. The idea of limiting the emission to 12 222 222 must reach your mind and consciousness, otherwise DASH is doomed.
Reply
1 point,4 months ago
This is false. MNOwatch clearly shows a high level of decentralisation in the network.
Reply
0 points,4 months ago
Mnowatch shows that Dash, a 10 years community, is ruled by 107 individuals.

https://mnowatch.org/Types/index.html?4=Yes

Is this decentralization? It is not!!!!! It is NOT!!! (let me repeat it once again, in case you cant hear it)

In the Encointer community I belong, a brand new and tiny community, we are already 75 persons !!!

https://mnowatch.org/votethenumbers/prepnumvote3/encointerinfo.php?

107 persons in 10 years, 75 persons in 2 years!!!!

Eat the dust, stupid masternodes, you are going straight into the pit of despair! You were meant to belong into that recycle bin, anyway!
Reply
-3 points,4 months ago
Limit emissions to 12,222,222
Reply
2 points,4 months ago
Are you still planning to release a stable version of Platform to Testnet (one that does not break Testnet) and invite everyone from the Dash community to attack it or are the Consensus issues pushing that plan back ? And are you planning to do this with or without the Masternode Voting feature ?
Reply
1 point,4 months ago
Yes, we are. And I still aiming to have this release this month where I want people to attack the system. It will be without the masternode voting feature. The masternode voting feature doesn't have a lot of work left, it's just that it hasn't been worked on a while as I wrote it, but then found that it would be best that I focus on other things.
Reply
2 points,4 months ago
As i understand it, this whole 'releasing a stable version of Platform to Testnet and invite everyone from the Dash community to attack it, was planned for this month ?
Reply
1 point,4 months ago
Yep, we are very close to that right now. I would say about a week away.
Reply
2 points,4 months ago
I hope the current Consensus issues are getting finished soon, so you can start working on Masternode Voting. I also hope that Consensus issues do not keep piling up like this, as it is clearly causing overall delay. Good to see that Dapi does not require a rewrite in Rust.
Reply