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

Title:Dash Core Group December Supplemental Funding Proposal
Owner:quantumexplorer
One-time payment: 1694 DASH (49058 USD)
Completed payments: 1 totaling in 1694 DASH (0 month remaining)
Payment start/end: 2023-12-10 / 2024-01-09 (added on 2023-12-15)
Votes: 508 Yes / 39 No / 1 Abstain

Proposal description

Dash Core Group December 26th Supplemental Funding Proposal

DCG already submitted 1 funding proposals for the budget cycle that pays out December 26th. This is a supplemental proposal that will fund Dash Core Group with an additional 1694 Dash:
1) DCG Compensation: 5,112 Dash per month (currently in month 1/3)
2) DCG Compensation Supplemental: 1694 Dash (currently in month 1/1)

What does this specific proposal fund?


DCG reserves are empty, this proposal aims to speed up recovery of a small buffer, so DCG can be in a more healthy position sooner.

How are things?

Things are actually starting to look quite bright, v20 was released and activated without a hitch. Before v20 many contributors were fearful of losing their job, or that they might not be able to afford to work for Dash. With the doubling of the treasury a great deal of optimism inside the team has sprung up as we look forward to 2024. On top of that stress tests of Platform are showing promising results which adds to the good mood inside of DCG.

When will DCG start hiring again?

We had continuously reduced staff during this bear market. Furthermore three months ago, the board of DCG decided out of necessity to let go of some long time contributors to the project which reduced our head count by about 1/3rd. This included almost the entirety of the business development and marketing/communication parts of Dash Core Group. This was a painful decision and one that will come with downsides.

As we move forward, business development and marketing/communication will most likely come from a different DFO. DCG will then be able to solely focus on software development for the network.

We have 1 critical hire in infrastructure that we are aiming to take place in February. Other hires will take place after we have at least 2 to 3 months of buffer.

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 December 26th superblock:
  • 1693 Dash ($55,022.5 USD @ $32.5 per Dash)
  •     1 Dash Proposal fee reimbursement
Total: 1694 Dash

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
3 points,7 months ago
@quantumexplorer
The 10% threshold logic seems to be completely messed up.
At the very least here within dashcentral, but potentially in Core as well.

The 10% threshold here is calculated right now: 285 more Yes than No votes
Core payment queue roundturn right now: 3194 (meaning the correct 10% threshold would be 320 more Yes than No votes)

The discrepancy is nearly 11% smaller than it should be, meaning the 10% threshold shown here is below 9% net votes.
Reply
2 points,7 months ago
It is messed up here on Dashcentral, it is not messed up on mnowatch or Core. https://mnowatch.org/leaderboard/
Reply
1 point,7 months ago
I have no problem giving ALL the remaining budget to DCG, as long as ALL DCG salaries are disclosed.

After all, DCG salaries SHOULD be disclosed because DCG is NOT a private company, it is a DASH public sector company.

And in ALL the public sector companies, the salaries are known.
Reply
2 points,7 months ago
DCG requesting close to 80% from our recently increased Treasury is just way too high.

All the previous DCG supplemental budget proposals that passed could not prevent DCG from running out of reserves this December, demonstrating just how inept these developers have been with regards to maintaining their reserves and their ability to cut back on their operational costs, when the situation required it from them. They were simply reacting to a changing market situation way too late.

Running out of reserves in December, requesting almost 80% of a Dash Treasury (that on DCG insist already doubled in size), still not being able to set a release date for Dash Platform on Mainnet, bypassing supermajority voting (10% treshold) in decision proposals whenever they feel like it (while at the same time not acknowledging simple vote majority on certain decision proposals that could work against DCG), those are all red flags for me right now.

Sam is already talking about hiring more developers, while Dash price is still pretty much at the bottom. Untill Dash price recovers and Dash is actually in a bull market again (maybe 6 months from now, maybe longer), DCG should not expend their number of developers and should just focus on activating the Dash Platform features, that are laying dormant in Dash Core v20.

Something they have been extremily vague about (Product Brief mentions Platform feautures activate with Dash Core v21, Pasta mentions Platform features activate with v20.1, latest development update mentions Platform features activate between v20.1 and v21). It is anything but clear.

Lets avoid old mistakes : hiring too many developers, needing to keep those developers at work, putting them on developing features not directly related to releasing Platform to Mainnet, thereby introducing feature creep into the Dash Core updates, needing more time to test all these new features, not getting around to actually testing important Platform features --> delay --> delay --> delay.
Reply
1 point,7 months ago
Talking about hiring more developers when we lost some in pretty critical places AFTER we have some buffer isn't a bad thing. For example we currently have 1 iOS dev. What happens if something happened to them or they quit? I am sure that you Qwizzie would be the first to cast a stone talking about how DCG should have prepared for this eventuality. Well that's what I'm trying to do, whatever is best for the project.

You generally have no idea what you are talking about, instead trying to infuse your view of the project into these comments. And the worst part is that by always being on here criticizing instead of contributing you are actually hurting the project. People who don't follow closely might think that DCG is just adding non vital features willy nilly. No, we want this out asap. Currently half the platform team is working on stress tests, the other half on finalizing withdrawals. You want to cut one of those?

Things are going well, this supplemental is here because with it DCG will be in a better position faster. This in turn will lead to better development outcomes which should translate to Dash doing better.
Reply
3 points,7 months ago
I am contributing by highlighting bugs in Dashmate on Github that should never been there in the first place and has threatened the stability of Dashmate on Mainnet. I am contributing by participating on the forum and on Dash Central by providing feedback on budget proposals, which as a masternode owner is my right and pretty much my duty. I am helping out when fellow MNO's have a problem and i happen to know the answer.

If you can't handle criticism when this project has known more delay then any other crypto project i know of and still the most asked question is 'When Evo', without you as CTO of DCG still having a clear answer for, then maybe don't respond at all.

I don't want current developers cut in halve, i want you to stop putting too much demand on the Treasury (80% ?) and don't extend the number of developers, untill we are in a bull market.
Reply
2 points,7 months ago
Thanks for the contribution reporting bugs on Dashmate, I did not know that, I apologize.

As for extending the number of devs, I would not do that except in critical situations with no bus factor which still would only happen after a few months, but would happen sooner if these proposals pass.
Reply
2 points,7 months ago
See : https://www.dash.org/forum/index.php?threads/dashmate-discussion.53951/page-4#post-237098
Reply
2 points,7 months ago
I even contributed by testing a fix for Dashmate on Mainnet (and inevitable getting a high PoSe score because of it). Turns out someone left wasm.dpp initialization code active in Dashmate that in Dashmate v0.25.13 did not form a problem, but in Dashmate v0.25.15 became a huge problem. I can confirm Dashmate v0.25.16 will have a fix for this, as Platform devs removed it as a dependency.
Reply
3 points,7 months ago
And then there are all those years of me testing Dash Core updates on Testnet. Starting all the way back with Evan and a small group of testers. Those good old days. I guess that was before your time, Sam. When testing was still done on dash.org/forum
Reply
2 points,7 months ago
And i want a clear answer if Platform features get activated with v20.1 or not.
Reply
1 point,7 months ago
Our approach with Core is designed for flexibility in activating platform, ensuring continuous development regardless of the timeline. Core is committed to delivering minor versions as new changes are ready. Therefore, the activation of the platform will coincide with the release of a Core version that aligns with platform's readiness. If platform is ready alongside Core v20.1, it will be included in that release. If platform is ready later, it will activate with the corresponding minor version available at that time.

In cases where testing of platform reveals the need for breaking changes, we will release these as version v21. This release, however, will be atypical for a major version. It will encompass only the essential features required for the platform's activation, diverging from our usual practice of expansive feature additions in major releases.
Reply
2 points,7 months ago
So in worst case scenario Platform features get activated through a hard fork in v21 (which will be limited in scope with regards to features). Best case scenario Platform features get activated through a hard fork in a minor version update (but DCG has no idea right now which one).

Leaving us in a situation that Core (through activation of v20) is pretty much done with regards to Platform and (as i suspected) the waiting is now on the Platform teams to :

* finish the stress testing phase (which is
* fix existing bugs (2 major bugs, a few minor)
* test and verify the Platform fee system and fix any bugs from there
* have each team code check other team's work
* check for and fix possible vulnerabilities / exploits

(third party library vulnerability for example : https://www.dash.org/forum/index.php?threads/hardware-wallet-ledger-connect-kit-library-hacked.54411/#post-237329)

After which Core can release the hard fork that will activate the Platform features.
Lets hope that will be somewhere early 2024, not late 2024.
Reply
1 point,7 months ago
* finish the stress testing phase (which is exceeding the planned 2 months by now, i think ? )
Reply
2 points,7 months ago
correction : stress testing is part of the overall testing phase, which looks to be outgrowing the reserved 2 months considerably.
Reply
2 points,7 months ago
Because the lack of clarity, change in plans / roadmap, constant delays, DCG not abiding the super majority (10% treshold) with decision proposals .. that is what is actually hurting this project.
Reply