Proposal “DCG-COMP-APR-JUN23“ (Completed)Back
| Title: | Dash Core Group Compensation April - June |
| Owner: | quantumexplorer |
| Monthly amount: | 2296 DASH (66371 USD) |
| Completed payments: | 3 totaling in 6888 DASH (0 month remaining) |
| Payment start/end: | 2023-03-12 / 2023-06-09 (added on 2023-03-09) |
| Votes: | 519 Yes / 93 No / 4 Abstain |
Proposal description
Dash Core Group March 26th Funding Proposals
DCG is submitting 3 funding proposals for the budget cycle that pays out December 26th:
1) DCG Compensation: 2,296 Dash per month (currently in month 1/3)
2) DCG Infrastructure: 459 Dash (currently in month 1/2)
3) 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, business development, marketing, and support staff. This is a multi-month proposal that will cover compensation for April through June 2023.
What is the proposal funding?
As of February 28th, 2023, DCG has 39 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 for a set defined period before returning as a volunteer.
Our run-rate for December will be around $220,000. With this current compensation proposal, we are asking for total funding of $133,168 per month. If this proposal passes, we will be consuming roughly $90,000 from our reserve per month. Our compensation reserve as of February 28th stands at slightly less than 5 months of compensation reserve. We built up reserves for the exact situation we find ourselves in today, where our compensation run-rate is higher than our compensation related revenue, due to a decline in the price of Dash. With the more recent uptick in the price of Dash we find ourselves in a slightly better situation where our compensation reserves (mostly held now in Dash) can last longer for us.
What is the current progress of development towards Evolution?
There are many components to Evo being able to be released.
RS-Drive (high level storage - storage of documents) - In Polishing - very little development currently ongoing as it is mostly done. Development on this component started in December of 2021.
GroveDB (medium level storage - storage of data representing components) - In Testing - absent some discovered issue GroveDB can be considered complete. Development on this component started in November of 2021.
Tenderdash (consensus component) - In Testing - absent some discovered issue Tenderdash can be considered complete for Mainnet launch. Development on this component started late 2020.
RS-DPP - In extreme development (most Platform devs working in this area currently) - Development on this component started mid 2021.
JS-Drive(-Abci) (execution) In Polishing - very little development currently ongoing as it is mostly done. Development on this component started in 2017. This component is stated to be replaced.
RS-Drive-Abci (execution) In current plan what is needed has been completed for Mainnet - some development currently ongoing as it is mostly done for Mainnet delivery. Development on this component started mid 2022. This component is stated to eventually replace JS-Drive-Abci. Our plan is to release with JS-Drive-Abci and as a fast follower switch to RS-Drive-Abci.
What are the current risks?
The model of using JS-Drive(-Abci) as the executor has taken more time than expected. We had gone down this path in the sake of speed to market, slightly against my better judgement at the time. As time goes on and there are more and more delays because of this architecture I personally believe that at some point we might need to make a switch. Another plan would be to complete the migration to RS-Drive-Abci. The reason this was not chosen immediately was twofold - it would have meant that we would have replaced almost all work prior to me being CTO - and speed of delivery. This is currently not the plan, however if there are more delays because of Javascript and bad architecture (from remnants of when I wasn't CTO) this switch will happen, mostly because at that point the switch to RS-Drive-Abci will get us to release faster to mainnet.
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.
Technology:
Core:
Communication / Business Development / Marketing:
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:
Note: Should any funding remain, we will apply it toward future compensation expenses and any related taxes.
DCG is submitting 3 funding proposals for the budget cycle that pays out December 26th:
1) DCG Compensation: 2,296 Dash per month (currently in month 1/3)
2) DCG Infrastructure: 459 Dash (currently in month 1/2)
3) 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, business development, marketing, and support staff. This is a multi-month proposal that will cover compensation for April through June 2023.
What is the proposal funding?
As of February 28th, 2023, DCG has 39 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 for a set defined period before returning as a volunteer.
Our run-rate for December will be around $220,000. With this current compensation proposal, we are asking for total funding of $133,168 per month. If this proposal passes, we will be consuming roughly $90,000 from our reserve per month. Our compensation reserve as of February 28th stands at slightly less than 5 months of compensation reserve. We built up reserves for the exact situation we find ourselves in today, where our compensation run-rate is higher than our compensation related revenue, due to a decline in the price of Dash. With the more recent uptick in the price of Dash we find ourselves in a slightly better situation where our compensation reserves (mostly held now in Dash) can last longer for us.
What is the current progress of development towards Evolution?
There are many components to Evo being able to be released.
RS-Drive (high level storage - storage of documents) - In Polishing - very little development currently ongoing as it is mostly done. Development on this component started in December of 2021.
GroveDB (medium level storage - storage of data representing components) - In Testing - absent some discovered issue GroveDB can be considered complete. Development on this component started in November of 2021.
Tenderdash (consensus component) - In Testing - absent some discovered issue Tenderdash can be considered complete for Mainnet launch. Development on this component started late 2020.
RS-DPP - In extreme development (most Platform devs working in this area currently) - Development on this component started mid 2021.
JS-Drive(-Abci) (execution) In Polishing - very little development currently ongoing as it is mostly done. Development on this component started in 2017. This component is stated to be replaced.
RS-Drive-Abci (execution) In current plan what is needed has been completed for Mainnet - some development currently ongoing as it is mostly done for Mainnet delivery. Development on this component started mid 2022. This component is stated to eventually replace JS-Drive-Abci. Our plan is to release with JS-Drive-Abci and as a fast follower switch to RS-Drive-Abci.
What are the current risks?
The model of using JS-Drive(-Abci) as the executor has taken more time than expected. We had gone down this path in the sake of speed to market, slightly against my better judgement at the time. As time goes on and there are more and more delays because of this architecture I personally believe that at some point we might need to make a switch. Another plan would be to complete the migration to RS-Drive-Abci. The reason this was not chosen immediately was twofold - it would have meant that we would have replaced almost all work prior to me being CTO - and speed of delivery. This is currently not the plan, however if there are more delays because of Javascript and bad architecture (from remnants of when I wasn't CTO) this switch will happen, mostly because at that point the switch to RS-Drive-Abci will get us to release faster to mainnet.
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.
Technology:
- CTO Samuel Westrich - quantumexplorer (making this proposal)
Core:
- 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
- Sr. Go Software Engineer
- Sr. Go Software Engineer
- Lead Rust/JS Software Engineer
- Lead Rust Software Engineer
- Senior Rust Software Engineer
- Senior JS Software Engineer
- Rust/JS Software Engineer
- Rust Software Engineer
- Rust Software Engineer
- Sr. JS Software Engineer
- Lead Tech Research Engineer
- Tech Research Engineer
Communication / Business Development / Marketing:
- Head of Business Development / Marketing
- Communication Officer
- Business Development Manager
- Lead Technical Content Developer
- Technical Content Developer
- HR Specialist
- Lead Infrastructure Engineer
- Infrastructure Engineer
- Infrastructure Engineer
- Lead SM / Project Manager
- SM / Project Manager
- Head of Product
- QA Engineer
- QA Engineer
- 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,295.66 Dash for core team compensation per month ($133,148 USD @ $58.0 per Dash)
- 0.33 Dash / per month proposal reimbursement
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
|
No comments so far?
Be the first to start the discussion! |
https://www.dash.org/forum/index.php?threads/dash-roadmap-update-with-eta.53528/#post-234582
At some point responsebility for this behavior will need to be taken and operational changes will need to be made to avoid this behavior in the future. Till that time consider my support gone.
nobody else has so many votes (except perhaps Binance has double as many MN, but we know they never vote!)
I guess this was posted before Dash price took a -16% nose dive today.
Yes from me.