Archived CDG: Multiple Governance Categories

[danielle]

Eric_Stanek
3
Jul '17

Description:
Our goal for the PIVX Governance system is to involve the community. That is why we call it Community Designed Governance. (CDG)
There are 2 extremely important changes taking place with the PIVX Governance System. These will drive many many smaller future changes.
The first, is that WHO can vote will be greatly expanded.
Voting will be completely redistributed such that it is no longer exclusive to the Masternode Owners (MNOs), and is inclusive of the PIVX Community as a whole. The MNOs accepted this in a historic landslide vote of 973 to 0. At the time, that represented more than half of the possible votes, which in itself is extremely significant. No other crypto-currency with Masternodes has made such a dramatic change in direction from being ruled by a small core group with the majority of votes, to a proper, well distributed and comprehensive, Community Designed Governance model.
This second, is that WHAT can be voted on, will be greatly expanded.
The purpose of this proposal is to expand voting to reach a much wider spectrum than simply where the treasury money will be spent.
For months now, on the PIVX Governance page 1 we have defined three treasury categories, but they have not yet been approved by the Masternode Owners. This proposal asks for that approval.
Funding:
This proposal asks for 100 PIV only. This includes 50 PIV to reimburse myself for the Proposal Submission Fee, and 50 PIV to reimburse the developer that must pay to finalise the proposal when it passes.
Proposal:
This proposal simply asks the following question:
Do you agree with the following high-level statement?

“PIVX will work towards a ‘Community Designed Governance’ system that dramatically expands the reach of voting power from simply Treasury Governance, to also include Manifesto Governance, and Protocol Governance.”

A YES vote means, you are voting that the following content will be added to the PIVX Governance page 1:

PIVX Masternode Owners have voted on and have accepted the following statement, as well as the three different treasury categories and their descriptions below:

“PIVX will work towards a ‘Community Designed Governance’ system that dramatically expands the reach of voting power from simply Treasury Governance, to also include Manifesto Governance, and Protocol Governance.”

A YES vote also means the Manifesto Governance description will be reworded to account for the fact that soon Masternode Owners will no longer have voting exclusivity. It will read as:

“This will very rarely – almost never – happen, and will require a high amount of participation (Metric not yet defined) during the voting process. Key is to make sure that even people in the community that typically don’t involve themselves with voting for proposals, are made aware a Manifesto Proposal has been submitted, and that they have been well informed of the issue(s) involved in a factual and unbiased way.”

A NO vote means, you are asking that the following content will be added to the PIVX Governance page 1:

PIVX Masternode Owners have voted and have rejected the following statement, as well as the three different treasury categories and their descriptions below:

“PIVX will work towards a ‘Community Designed Governance’ system that dramatically expands the reach of voting power from simply Treasury Governance, to also include Manifesto Governance, and Protocol Governance.”

Reference:
For clarity and for future reference, included here is the wording of the 3 categories at the time of writing for this proposal.

Manifesto Governance:

This will very rarely – almost never – happen, and will require a high amount of participation (Metric not yet defined) by Master Node Owners (MNOs) during the voting process. Key is to make sure that even MNOs that typically don’t involve themselves with voting for proposals, are made aware a Manifesto Proposal has been submitted, and that they have been well informed of the issue(s) involved in a factual and unbiased way.

Treasury Governance:

These proposals are the most common and are for allocating funds in the monthly treasury budget. These funds can be used for anything related to support PIVX. It may be overhead costs for servers, or Google Apps etc., or it may be for advertising, or to help launch a business that could not be justified otherwise.

Protocol Governance:

These proposals are zero cost and are to make decisions to change the code base (the protocol) of, or the priorities of changes to, the PIVX system. If such a decision requires funding, then that funding portion would be a separate Treasury Governance proposal submitted after the Protocol Governance proposal has been accepted. What is unique about Protocol Governance is that the Core Developers can veto such proposals if they are technically impossible, or logistics dictate an order of implementation different that that voted on in the proposal.

Vote Details:
Title: cdg-categories
Hash: 7092bdc755337d24252f8a6bc17ad3eed34db75de5eb0dcb54f8eef6570b0d70
To Vote in favor or Yes:
“mnbudget vote-many 95c013214770bf7b14049752f30a7b6c30573c58303595cbb6277feb3b9e826a yes”
To Vote against or No:
“mnbudget vote-many 95c013214770bf7b14049752f30a7b6c30573c58303595cbb6277feb3b9e826a no”
To check the Vote status:
“mnbudget getinfo cdg-categories”