Proposal “Dash-Core-Group-Comp-Feb-May“ (Active)Back

Title:Dash Core Group Compensation (February - May)
Owner:glennaustin
Monthly amount: 2663 DASH (257500 USD)
Completed payments: no payments occurred yet (4 month remaining)
Payment start/end: 2021-01-12 / 2021-05-11 (added on 2021-01-06)
Votes: 878 Yes / 38 No / 1 Abstain
Will be funded: Yes
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many 26cf6b05e0085d84897d7ae7cd3a36b22a04fa4269d86e1cbac538cf55389661 funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

Dash Core Group February 1st Funding Proposals
DCG is submitting 3 funding proposals for the February 1st budget cycle:
1) DCG Compensation part 1: $247,500 per month (February - May)
2) DCG Compensation part 2: 266 Dash per month (currently in month 3/3)
3) DCG infrastructure: 266 Dash per month (currently in month 3/3)

This proposal
This is cross-posted here

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 February through May.  Normally our compensation proposals span 3 budget cycles.  Since the Dash block reward reduction this year will occur in May, we are submitting a 4 month proposal to align our budget request with the reduction.  This allows us to avoid submitting a 3 month proposal followed by a 1 month proposal. 

What is the proposal funding?
As of January 6th, 2020, DCG has 30 paid staff associated with the project. In addition, we have 2 volunteers who have decided to work for no compensation. Out of the 30 paid staff, 2 have volunteered to reduce their salaries while we face budget constraints. In total 4 volunteers are working for reduced or no compensation.  For more detail to DCG’s team please follow this link: https://www.dash.org/dcg/

Our run-rate in February will be ~$215,000 after taking into account voluntary pay reductions. 
With this proposal, we are asking for total funding of $247,500 per month. At the current Dash price of $93 and assuming this compensation proposal passes we will be continuing to put additional funds into our compensation reserve.  We recently achieved an important initial milestone of building our compensation account to a 3 month reserve.  As a reminder, we target, at a minimum, a three month reserve in our compensation account and ideally six months to endure sustained periods of revenue impact.

If you would like more detail on DCG’s staff, financials, roadmap, and summary of our most recent accomplishments refer to our most recent quarterly call: https://www.youtube.com/watch?v=uNkRtaAyjYQ
Note that in the appendix of the quarterly call presentation we also publish an org chart.  An updated quarterly call will be provided later this month (January 2021). 

If you have any questions, please direct them to @glennaustin at dashcentral to ensure we are notified of your request.

Requested funding is as follows for the February through May budget cycles:
·   2,661.75 Dash for core team compensation per month ($247,500 USD @ $93 per Dash)
·          1.25 Dash / per month proposal reimbursement 
Total: 2,663 Dash per month

Note: Should any funding remain, we will apply it toward future compensation expenses and related taxes.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
0 points,8 days ago
@glennaustin I've read the letter that Ryan Taylor wrote about his objection to Dash being labelled a privacy coin. Sending this letter is most likely not going to do anything. I realise now why this issue has not been resolved when I raised it to you in one of your previous funding requests. Glenn said that nobody had taken any action when you had sent them emails. Well, the reason is we have not taken the right actions for this issue to be resolved. You may think sending an email or a letter is going to do the job but I can tell you from experience it definitely won't.

I can tell that neither Glenn nor Ryan have had real world professional sales experience. If you did you would have got this sorted out by now. Things of this nature have to be dealt with in the right way, with the right actions, to the right people, at the right time.

Firstly, what I would do if I was in your position is to ring up the government agency involved and network via phone calls to find out who is most like the right person/s to deal with this issue. Then call and speak with them directly with the aim of setting up a face to face meeting about this issue with them. The goal of the call is not to discuss in details the issues. The goal of the call is to inform them of the issue and that you need a face to face appointment to discuss this issue. The best way to deal with this is a face to face meeting but if not a video call. Without clearly identifying the person responsible you have next to no chance of getting this issue resolved.

If, for some reason you can't get a face to face meeting then you can try sending the letter but it needs to be addressed at least to a specific person - as senior as possible. When I saw that you started the letter "To whom it may concern" I realised you had not taken the time to actually identified a specific person responsible yet. We need to have the letter addressed to a specific senior person so that they are changed with the responsibility of dealing with it or, at the very least, they will pass it to the right person.

We should not send the letter to more than one person because if you do each can pass the responsibility to someone else. We need to send the letter to the best possible senior person that is likely to deal with the enquiry and then follow up with a call 1 week later. If in doubt send it to the most senior person that you have identified.

The most senior person should be identified because they will delegate it down to the right person. Senior people know the system and will know who will deal with it. This is why this letter should go to the most senior person you have identified. Also think about it, if a boss hands someone an action they are more likely to deal with it rather than the other way around.

Next the letter should be sent through an official legal means of registration. In the EU they use a service called a BureauFax method. This is not a fax but a special type of registered letter that can be used in a court of law as proof of notification to the party involved. When someone receives this type of communication is subtly informs them that legal proceedings could possibly happen in the future.

The letter should not go into all the details of why there is a misclassification but simply state that:

a) the technical classification is inaccurate and has been incorrectly made by this government agency.

b) there have been financial damages due to exchanges erroneously de-listing Dash based on their report findings.

The letter should state that you want to deal with this in an amicable manner however the issue needs to be dealt with some urgency because they have misrepresented Dash project and it is causing serious financial damages.

I would then request a face to face meeting with that person and for any others that are involved to be present at that meeting, or at the very least a video conference with them.

To find the right person you will have to ring around and speak to numerous people to find the right person. It is critical that you identify the most likely person to deal with this issue.

Without assigning a specific person responsibility nothing will happen. Nobody is going to selectively pick up and take responsibility of this issue. We need to assign someone that responsibility and if they feel that they are not the right person they will pass it on to the right person. However once you send a legal documents to a named person they know they have a responsibility to deal with it.

This type of issue cannot be dealt with via letters, emails or phone calls. We need face to face meeting with all people involved. If you can't do that then this issue is most likely never going to be resolved.
Reply
1 point,7 days ago
@DeepBlue. Thank you for your note.
The approach you describe is the exact one we have been taking. Thank you for validating our strategy.
As you can imagine, the resolution to this issue is slow-moving and time consuming but we are making progress.
Reply