Governance:

Our goal for the PIVX Governance system is to involve the community. We’ve got a long way to get there, but soon we expect to be making huge initial steps. This process will take a long time, and we call it Community Designed Governance.

 

PIVX Masternode Owners have voted and have accepted the following statement:

“ PIVX will work towards a ‘Community Designed Governance’ system that changes the distribution of votes, to include the entire PIVX community.”

 

The following explains the 3 areas of the Governance system and how voting is managed. All areas of DAO Governance follow the same process in terms of submitting a proposal, and Master Node Owners voting to accept/reject the proposal. Such voting can only happen at each Super Block. (Roughly once per month.)

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.”

 

There are 3 types of Proposals:

Manifesto Governance:

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.

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.