Dash Governance by Community - DGbC
The idea sparked into my mind the other day, following some forum discussions and some official Slack discussions.
I personally hate seeing funds go to waste each month, in a sense that they’re there, ready and available, yet don’t get used because all the proposals don’t add up to the exact available amount.
Some out-voted proposals exceed the available total, or others get down-voted, so they’re not funded. This leaves a gap each month where funds are not produced, nor burned. In essence, they’re useless.
My idea would be a month-to-month proposal that attempts to “fish” these remaining funds and allocate them to further the development of Dash. They would be held and managed by the community.
The workflow would mimic that of DGbB. Anyone in the community can propose a project, and put it up to vote.
If the vote is passed, the requested funds are sent, and the project monitored by the community.
It would necessarily need to be a month by month only thing, as the amount is completely unpredictable.
If the vote(s) do not pass or there are funds left overs, these roll over to the next month.
Don’t want to get too ahead of myself, this is not a formal presentation, but a feeler pre-proposal/discussion thread.
How do you feel about this so far? Ask me hard questions.
Brainstorm Addendum:
- If this were to to happen and fail, the 'fished' funds can be either burnt, donated to the Foudation, or any other end, voted on formally by Masternode from a formal proposal to the DGbB.
- Funds held in a multisig address by veteran team&community members
- no project can exceed 33% of total fund, and after 3 funding rounds all remaining funds are liquidated or burnt to prevent fund build-up / greed down-vote / risk exposure.
.
The idea sparked into my mind the other day, following some forum discussions and some official Slack discussions.
I personally hate seeing funds go to waste each month, in a sense that they’re there, ready and available, yet don’t get used because all the proposals don’t add up to the exact available amount.
Some out-voted proposals exceed the available total, or others get down-voted, so they’re not funded. This leaves a gap each month where funds are not produced, nor burned. In essence, they’re useless.
My idea would be a month-to-month proposal that attempts to “fish” these remaining funds and allocate them to further the development of Dash. They would be held and managed by the community.
The workflow would mimic that of DGbB. Anyone in the community can propose a project, and put it up to vote.
If the vote is passed, the requested funds are sent, and the project monitored by the community.
It would necessarily need to be a month by month only thing, as the amount is completely unpredictable.
If the vote(s) do not pass or there are funds left overs, these roll over to the next month.
Don’t want to get too ahead of myself, this is not a formal presentation, but a feeler pre-proposal/discussion thread.
How do you feel about this so far? Ask me hard questions.
Brainstorm Addendum:
- If this were to to happen and fail, the 'fished' funds can be either burnt, donated to the Foudation, or any other end, voted on formally by Masternode from a formal proposal to the DGbB.
- Funds held in a multisig address by veteran team&community members
- no project can exceed 33% of total fund, and after 3 funding rounds all remaining funds are liquidated or burnt to prevent fund build-up / greed down-vote / risk exposure.
.
Last edited: