Proposal “DCG-COMP-JUL-SEP23“ (Completed)Back

Title:Dash Core Group Compensation July - September
Monthly amount: 2558 DASH (74055 USD)
Completed payments: 3 totaling in 7674 DASH (0 month remaining)
Payment start/end: 2023-06-11 / 2023-09-09 (added on 2023-06-12)
Votes: 529 Yes / 94 No / 6 Abstain

Proposal description

Dash Core Group June 26th Funding Proposals

DCG is submitting 2 funding proposals for the budget cycle that pays out June 26th:
1) DCG Compensation: 2,558 Dash per month (currently in month 1/3)
2) DCG Supplemental proposal: TBD on amount.

What does this specific proposal fund?

This proposal funds Dash Core Group's ongoing compensation costs - including all developers, administrative, and support staff.  This is a multi-month proposal that will cover compensation for July through September 2023.

What is the proposal funding?

As of May 31st, 2023, DCG has 37 paid staff associated with the project. In addition, we have 1 volunteer who has decided to work for no compensation and 1 person who has decided to work at minimal compensation. Since the last proposal we have been forced due to market conditions to let go of 2 individuals, 1 QA and 1 developer in the Platform team. On top of this 1 non developer that was previously at full time is now at half time.

Our projected run-rate for July will be around $210,000. With this current compensation proposal, we are asking for total funding of $74,427 per month. If this proposal passes, we will be consuming roughly $135,000 from our reserve per month. Our compensation reserve as of June 13th stands between 2 and 3 months of compensation reserve. While receiving around 75k USD /month worth of Dash from the Treasury as well, we should be able to operate without drastic structural changes for around 4 more months. This is obviously not a desired situation and we are working alongside non DCG members to find out how to best ensure that the bear market does not have a high impact to development efforts.

Why no infrastructure proposal?

DCG has for the past few years offered two proposals, one for 50% of the budget  treasury for compensation, and one for 10% for infrastructure/marketing/legal/business dev. Then we also submitted a supplemental for whatever funds were leftover in the treasury. As it currently stands our infrastructure budget does not need replenishing and is in a very good state. For the next 3 cycles we will instead only submit 1 main proposal for compensation requesting 60% of the budget of the treasury.

What does DCG's current structure look like?

DCG has evolved to primarily be a tech focused organization that can be grouped into 2 main parts, technology and technology support.


  • CTO Samuel Westrich - quantumexplorer (making this proposal)

  • Lead C++ Software Engineer
  • Lead C++ Software Engineer
  • Senior C++ Software Engineer
  • Senior C++ Software Engineer
  • C++ Software Engineer
  • Lead Android Software Engineer and Principal Developer
  • Sr. Android Software Engineer
  • Android Software Engineer (Part time)
  • Sr. iOS Software Engineer
  • Sr. iOS Software Engineer
Platform Consensus
  • Sr. Go Software Engineer
  • Sr. Go Software Engineer
Platform Protocol
  • Lead Rust/JS Software Engineer
  • Lead Rust Software Engineer
  • Senior Rust Software Engineer
  • Rust/JS Software Engineer 
Platform Database (GroveDB)
  • Rust Software Engineer
  • Rust Software Engineer
Platform SDK
  • Sr. JS Software Engineer
  • Lead Tech Research Engineer
  • Tech Research Engineer
Technology Support:

Communication / Business Development / Marketing:
  • Head of Business Development / Marketing
  • Communication Officer
  • Business Development Manager
  • Lead Technical Content Developer
  • Technical Content Developer
Human Resources:
  • HR Specialist
  • Lead Infrastructure Engineer
  • Infrastructure Engineer
  • Infrastructure Engineer
Project Management
  • Lead SM / Project Manager
  • SM / Project Manager
  • Head of Product
Quality Assurance
  • QA Engineer
Tech Support
  • Lead Support Engineer
  • Support Engineer
  • Web Developer

If you have any questions, please direct them to @quantumexplorer at dashcentral to ensure we are notified of your request.
Requested funding is as follows for the December through February budget cycles:
  • 2,557.66 Dash for core team compensation per month ($74,427 USD @ $29.10 per Dash)
  • 0.33 Dash / per month proposal reimbursement 
Total: 2,558 Dash per month
Note: Should any funding remain, we will apply it toward future compensation expenses and any related taxes.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
1 point,11 months ago
Decided to change my votes from ABSTAIN to NO.
4 points,1 year ago
Yes. DCG has vastly improved in transparency and communication. Development output and quality is up (yes, despite the halt). Sam and the rest of the team are doing great work. I'm not going to focus on the market and the regulators, let's ship this shit and get evo out there, build on it and grow.
-3 points,1 year ago
Such is the confidence, this was written for the future date, "November 31st, 2023".

But yeah, no remorse for the first - but not the last - 16+ hour chain halt. In any other organization you'd of been fired already, fat chance of that happening here though.

1. Any news regarding the SEC yet?

2. Regarding the SEC or the PoS sidechain, is there any statement you would like to make now that you might later rely on in defense?

3. In hindsight, do you continue to standby your decision to choose a PoS sidechain?

4. If dash was a _protocol_ there would be more than one independent masternode daemon. Will you initiate development to convert your _product_ to a _protocol_?

You do, of course, have the right to remain silent.
5 points,1 year ago
Sorry for the oversight writing November and not May, fixed.

As for the chain halt, it was and still is a terrible situation, we have explained what the issue was. If you want to hear it here it is: DCG leadership and staff are very sorry that such an event happened. We continuously strive for high quality code and testing. This event scenario was not caught in our testing and we will improve our testing framework in the future. However I can not say that such an event will ever take place again because such in the nature of development. No much more that a NASA or SpaceX lead engineer or manager could say that no rocket will ever explode again.

Here are the answers to your questions:

1. Question: Any news regarding the SEC yet?

We have no extra information compared to what has been made public.

2. Question: Regarding the SEC or the PoS sidechain, is there any statement you would like to make now that you might later rely on in defense?

First, a side note. The Platform chain has many elements of PoS, if might very well be considered PoS, but since different people have different understanding of what PoS is and there's no concrete definition that I am aware of, we need to be careful about saying that Platform is PoS right now.
It is important to understand that demand is created on the Platform chain, however supply is solely created by Masternodes/Miners on the Core chain, I do not know of any PoS blockchain that does not issue it's supply. No native coins/tokens are created on the Platform chain, instead it uses a form of wrapped Dash issued on the core Chain.

3. Question: In hindsight, do you continue to standby your decision to choose a PoS sidechain?

I stand by the decision to go with a heavily modified Tendermint. It was however, originally, not my preferred approach. The decision to use a modified Tendermint was decided by the Platform team and the previous CTO. I had previously advocated for a slightly more custom approach that I believe would have been more scalable. It's hard to know if my previous solution or this solution would have been better. In the end we have a very good system that has shown to work well. It will offer more than a good enough user experience through the first few million users.

4. If dash was a _protocol_ there would be more than one independent masternode daemon. Will you initiate development to convert your _product_ to a _protocol_?

You are mistaken if you think this isn't the case. Dash Core has a protocol, dash platform as well. There is a protocol number that defines consensus. Other versions of Dash Core (maybe written in other languages) could connect to the network and function as well if they run the same protocol.
2 points,1 year ago
Thank you for the reply.

Which alternative daemon(s) not developed or maintained by DCG that I can run for a masternode? If the answer is none then I say you have a product, it is a protocol by name only..I feel this distinction is vital and, ultimately, this was a single point of failure of the masternode network.

Going forward, I feel DCG should cease publishing all server side code, including binaries, as DCG holds too much influence. In such circumstance, how could alternatives truly flourish or be considered equal? I would like to hear alternative ideas to this.

Don't get me wrong, Of course, I welcome more thorough testing but I am also hungry for changes that could dilutes influence from a few heavyweights here.
2 points,1 year ago
dashd-go repo is held by DCG but manaintained by Alex for the Maya integration. I think
1 point,1 year ago
Just had a quick glance at the github which says, by design, there is no wallet functionality. I'm not sure how useful this implementation is for running masternodes. And I'm also not clear of DCG's role / influence with this.

But do please keep us informed. I would love to run an independent implementation so long as it didn't interfere with upgrades and payouts.
0 points,1 year ago
1 point,1 year ago
Would you like to reset this animosity?