Pre-Proposal Discussion - Jury Duty
Civilized societies have been calling groups of people together to discuss issues as long as there have been societies. In Scandinavia this process was called a "thing". This was the governing assembly made up of the free people of the community. In the Old Testament we find this: Deuteronomy 25:1: "If there be a controversy between men, and they come unto judgment, that the judges may judge them; then they shall justify the righteous, and condemn the wicked."
In the modern DASH world, we have a similar need. Every month, budget proposals must be voted on by the masternode owners of the community. As time goes on, these proposals become more complex. This proposal will formalize the responsibilities of said masternode owners towards digesting this material.
Basic Idea
Each month a quorum of masternode owners will be selected at random from the list of active masternodes. These owners shall meet online to discuss the merits of the current batch of budget proposals. It is their job to separate the "righteous" from the "wicked".
Practical Considerations
There are hundreds of options for small groups to collaborate online. Try this search in your browser: "free online collaboration tool". One of these options can be used. 10 masternodes can be selected at random quite easily as this function already exists. These 10 Jurists will meet to discuss the merits of each proposal. At the end of their deliberations, they will create a summary of their findings with a post on dashtalk (or it's successor). The penalty for skipping Jury Duty is a one-time skipping of the next payment for that masternode.
Cost of Implementation
Members of the core team can be canvassed regarding how much work this will be to implement. It should be minimal. This work can be performed by internal programming talent or outsourced.
Rationale
Owning a masternode should involve more than simply collecting payments every X number of days. It should involve some research into the future of DASH and insuring the success of the project. Remember what Uncle Ben famously said:
Civilized societies have been calling groups of people together to discuss issues as long as there have been societies. In Scandinavia this process was called a "thing". This was the governing assembly made up of the free people of the community. In the Old Testament we find this: Deuteronomy 25:1: "If there be a controversy between men, and they come unto judgment, that the judges may judge them; then they shall justify the righteous, and condemn the wicked."
In the modern DASH world, we have a similar need. Every month, budget proposals must be voted on by the masternode owners of the community. As time goes on, these proposals become more complex. This proposal will formalize the responsibilities of said masternode owners towards digesting this material.
Basic Idea
Each month a quorum of masternode owners will be selected at random from the list of active masternodes. These owners shall meet online to discuss the merits of the current batch of budget proposals. It is their job to separate the "righteous" from the "wicked".
Practical Considerations
There are hundreds of options for small groups to collaborate online. Try this search in your browser: "free online collaboration tool". One of these options can be used. 10 masternodes can be selected at random quite easily as this function already exists. These 10 Jurists will meet to discuss the merits of each proposal. At the end of their deliberations, they will create a summary of their findings with a post on dashtalk (or it's successor). The penalty for skipping Jury Duty is a one-time skipping of the next payment for that masternode.
Cost of Implementation
Members of the core team can be canvassed regarding how much work this will be to implement. It should be minimal. This work can be performed by internal programming talent or outsourced.
Rationale
Owning a masternode should involve more than simply collecting payments every X number of days. It should involve some research into the future of DASH and insuring the success of the project. Remember what Uncle Ben famously said:
