DeepBlue
Active member
Part 05: Decentralised Decision Making: The Dash Masternodes Association
This post is to discuss the setting up of the Dash Masternodes Association (DMA).
The current problems this would address are:
1. Declining MNO contributions: The declining interest and participation of MN in governance decisions
2. Continuity Ensuring continuity in governance decisions
3. Consistent decisions that align with Dash's core values and target markets: How to make sure that we make decisions based on Dash's target markets, Dash Goals as outlined in the Dash Decentralisation Charter document. https://www.dash.org/forum/threads/...-the-dash-decentralisation-charter-ddc.50379/
4. Making Better quality decisions as MNOs do not have time to thoroughly assess proposals would delegate their keys to members of Dash Masternode Association to assess projects and make their recommendations to MNOs that have delegated their voting keys.
5. Accountability. Ability to ensure project owners, including DCG and the DIF are held properly accountable to the network for their funding spends and decisions.
Currently with the Governance system there is lack of quality participation from the great majority of Masternodes. In many cases the votes for a proposal only come on the very last day of the proposal with very few constructive comments or criticisms of a project that has been put forward for funding in the Governance system. Unfortunately this means that poor governance decisions are still being made and valuable resources are being lost to obvious dead-end projects. In addition proposal owners do not feel accountable to a diverse group of masternodes who have a huge variety of ideas on how the DASH project should move forward. The great majority of Masternodes are not contributing their business experience and constructive comments to proposal owners. As a consequence we are not getting the best use of our investment money.
Another major problem is enforcing accountability on important projects such as Dash Core Group. Currently because MNOs are contributing independently as individual entities their voice is not that strong. As a consequence DCG often just ignore MNOs that are asking for greater clarity and accountability. What would be much better is to have an appointed Masternode Association in which a small group of Masternodes with established experience in business be set up and MNOs that do not have the time to properly assess project delegate their voting keys to specific members of the Masternode Association who they feel can make a better voting decision than they have time for. This would lead to more accountability for proposal owners and better quality decisions for the network.
One very important point to make clear is that each Masternode has the ability at any time to withdraw their voting keys from anyone in the Masternode association if they do not agree with their decision making. As long as a MNO has the power to withdraw their voting key at any time then the decision making is still in a decentralised driven decision.
What is absolutely clear is that there is not sufficient quality contributions being made by MNOs in assessing projects and this has to change in order for the project to be successful in my opinion. If we do not get the Governance system working efficiently for us then we will continue to make erratic and illogical business decisions and the DASH project will, in my opinion, eventually fail. We must make changes now so that we can start making solid,business decisions to get the project performing again.
I feel that in order for the governance system to be effective we need to separate the actions of assessing projects and holding project owners accountable from approval of that assessment.
Masternodes in the appointed masternode association would be required to give their logical reasoning for why they recommend MNOs go with their recommendation for voting on a project. The logic would be clearly laid out and MNOs could then assess if they want their voting keys to stay with the MN in the DMA or not.
Once a MN in the association has clearly stated how they intended to vote and the reasons for their vote decision would be clearly written out. Once a decision was made by a MNO in the association it could not be changed before a specified time in the voting cycle so that MNOs that have delegated their voting keys have an opportunity to revoke their keys if they are not happy with the voting decision made by any MNO.
Each MNO in the DMA would declare their areas of expertise so that MNOs who want to delegate their voting keys can feel confident that decisions made in those areas will be based on actual experience and not hearsay. If necessary DashWatch could run an optional confidential audit on the MNO to ensure they have the experience they say they have.
The benefit of the DMA for the DASH network would be better quality decisions being made with still the option to withdraw voting keys if MNOs are not happy with the performance of a MNO who is voting on their behalf.
The MNO association would also be responsible for other tasks such as drafting the Dash Decentralization Charter which I posted more information on here:
https://www.dash.org/forum/threads/...-the-dash-decentralisation-charter-ddc.50379/
I would be interested in what other MNOs think about the concept of setting up the Dash Masternode Association to improve our governance decision-making and to help build the Dash Decentralization Charter.
This post is to discuss the setting up of the Dash Masternodes Association (DMA).
The current problems this would address are:
1. Declining MNO contributions: The declining interest and participation of MN in governance decisions
2. Continuity Ensuring continuity in governance decisions
3. Consistent decisions that align with Dash's core values and target markets: How to make sure that we make decisions based on Dash's target markets, Dash Goals as outlined in the Dash Decentralisation Charter document. https://www.dash.org/forum/threads/...-the-dash-decentralisation-charter-ddc.50379/
4. Making Better quality decisions as MNOs do not have time to thoroughly assess proposals would delegate their keys to members of Dash Masternode Association to assess projects and make their recommendations to MNOs that have delegated their voting keys.
5. Accountability. Ability to ensure project owners, including DCG and the DIF are held properly accountable to the network for their funding spends and decisions.
Currently with the Governance system there is lack of quality participation from the great majority of Masternodes. In many cases the votes for a proposal only come on the very last day of the proposal with very few constructive comments or criticisms of a project that has been put forward for funding in the Governance system. Unfortunately this means that poor governance decisions are still being made and valuable resources are being lost to obvious dead-end projects. In addition proposal owners do not feel accountable to a diverse group of masternodes who have a huge variety of ideas on how the DASH project should move forward. The great majority of Masternodes are not contributing their business experience and constructive comments to proposal owners. As a consequence we are not getting the best use of our investment money.
Another major problem is enforcing accountability on important projects such as Dash Core Group. Currently because MNOs are contributing independently as individual entities their voice is not that strong. As a consequence DCG often just ignore MNOs that are asking for greater clarity and accountability. What would be much better is to have an appointed Masternode Association in which a small group of Masternodes with established experience in business be set up and MNOs that do not have the time to properly assess project delegate their voting keys to specific members of the Masternode Association who they feel can make a better voting decision than they have time for. This would lead to more accountability for proposal owners and better quality decisions for the network.
One very important point to make clear is that each Masternode has the ability at any time to withdraw their voting keys from anyone in the Masternode association if they do not agree with their decision making. As long as a MNO has the power to withdraw their voting key at any time then the decision making is still in a decentralised driven decision.
What is absolutely clear is that there is not sufficient quality contributions being made by MNOs in assessing projects and this has to change in order for the project to be successful in my opinion. If we do not get the Governance system working efficiently for us then we will continue to make erratic and illogical business decisions and the DASH project will, in my opinion, eventually fail. We must make changes now so that we can start making solid,business decisions to get the project performing again.
I feel that in order for the governance system to be effective we need to separate the actions of assessing projects and holding project owners accountable from approval of that assessment.
Masternodes in the appointed masternode association would be required to give their logical reasoning for why they recommend MNOs go with their recommendation for voting on a project. The logic would be clearly laid out and MNOs could then assess if they want their voting keys to stay with the MN in the DMA or not.
Once a MN in the association has clearly stated how they intended to vote and the reasons for their vote decision would be clearly written out. Once a decision was made by a MNO in the association it could not be changed before a specified time in the voting cycle so that MNOs that have delegated their voting keys have an opportunity to revoke their keys if they are not happy with the voting decision made by any MNO.
Each MNO in the DMA would declare their areas of expertise so that MNOs who want to delegate their voting keys can feel confident that decisions made in those areas will be based on actual experience and not hearsay. If necessary DashWatch could run an optional confidential audit on the MNO to ensure they have the experience they say they have.
The benefit of the DMA for the DASH network would be better quality decisions being made with still the option to withdraw voting keys if MNOs are not happy with the performance of a MNO who is voting on their behalf.
The MNO association would also be responsible for other tasks such as drafting the Dash Decentralization Charter which I posted more information on here:
https://www.dash.org/forum/threads/...-the-dash-decentralisation-charter-ddc.50379/
I would be interested in what other MNOs think about the concept of setting up the Dash Masternode Association to improve our governance decision-making and to help build the Dash Decentralization Charter.
Last edited: