Questions for Ryan Taylor:
1. What would you say to people who believe that DASH is becoming centralized organization through the expansion of the core team and it's varied business activity groups who are not being transparent in their activities and not willing to separate out the different core divisions to individual funding requests?
I am aware that there is a legal structure in place where MNOs could theoretical "fire" the core team. However, if the entire core team composes of many grouped and diverse activities for DASH that are important for the network to survive how can we do this? If all the different activities such as Code Development, Business Developement, Marketing, PR etc are all grouped in the same funding compensation request doesn't this negate the legal structure put in place? It would be near impossible for MNOs to vote out the core team with all divisions being grouped together. If we needed to do this it would pull the whole management of the DASH organization down in one fail swoop. If however we had separate sDAO's (sub-DAOs) for each DASH core business activity then it might be possible to "fire" or preferably make suggestions for improvement of a division without causing damage to the rest of DASH management.
2. Would the core team be willing to consider to separate out different core team activities into separate funding requests for treasury funds so they are more accountable to the MNOs questions in their funding requests? If not why not?
3. Why are the core team proposal owners in the majority of cases not responding to questions by MNOs posted in their requests for funding? I have heard reasons such as we are "too busy", we are working on being more transparent etc etc. However transparency is not something that requieres working on. The proposal owners just need to answer the questions posted by MNOs in their proposals. As for not having enough time, answering questions only takes a few hours per proposal. Time can be made for that. I have listed a small sample of reasons (14) given why core do not respond to questions in my posting in this thread:
https://www.dash.org/forum/threads/dcg-and-non-core-functions.39457/
Background to these questions:
My view is that DASH is becoming a centralized financial organization. This is occuring through the ever expanding core team that is choosing not to be held accountable to the MNOs questions in their funding proposal requests. To date unwilling to break up their different divisions of core to separate funding requests and answer my questions and others MNOs questions in their proposals. DASH is looking more like a commercial organization on a daily basis.
I think this centralization of the expanding core team with non developmental roles (e.g. marketing, business dev etc) could well be a factor affecting the DASH position fall from 4th to 15th position in coinmarket cap. A centralized organization is putting off investors who are choosing lesser coins than DASH but who are maintaining the values of true decentralziation. I have to say personally I am feeling that way myself.
Grouping all salaries together so that we cannot vote out or comment on individual divisions of the core team is not operating as a decentralizated organization. It is a centralized organization, even if the people themselves are based in different geographical locations. It makes no difference because the decisions and money are all going to one central body, and that central body, currently referred to as "core team" is not being transparent. I've heard all the reasons given e.g. "we don't have enough time", "what would you rather we do answer your questions or get on with work etc etc etc.
The fact remains the core team has a responsibility to answer MNO questions in funding requests whether they like it or not. That is how DASH was setup.
Invariably I have received little to no response from the core team to requests for information on their proposals. Much of how core are setup and operate is kept private, away from scrutiny from the MNOs and the DASH community. No matter how busy the core team are time needs to be made to adhere to the requirements that proposal owners are accountable to answering MNO's questions about their funding requests. There are no questions on this point. The core team are accountable to the investors.
Isn't one of DASH's core values "Radical Transparency"? With secrecy comes unaccountability, potential corruption and doubt.
Wasn't the reason to run an open source project so that we would live up to our values of "radical transparency" and in so doing ensure that corruption and the devastating results from it cannot occur?
All other proposal owners respond to questions posted by the MNOs *except core proposal owners* who only answer very few questions.
One of the primary reasons I became interested in crypto was due to the financial world crisis in 2008 that wiped out the livelihoods of millions of people. This decimation of the world economy happened as a direct consequence of large financial institutes such as Lehman Brothers and Goldman Sacks keeping their working activities secret. In this way they were able to set up an environment where they could do what they wanted - ultimately cheating the world out of their money. This cannot be allowed to happen with DASH.
DASH core team are becoming a large centralized organization. If we do not step in now to stop this then DASH cannot be called a decentralized organization any longer and we are open to all the same issues that have happened with the World financial crisis in 2008 with the Lehman Brothers.
"Radical transparency" is just one key component in ensuring that we can trust an organization. In addition no organization should be so big that it becomes "too big to fail". This is now the case with the core team. All their proposals on core team compensation go through. Because they have to go through. If however core is split up into separate subDAOs and and these have their own funding requests we are in a much healthier environment for debate to improve or replace core team members that are not performing.