• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Treasury System Hard Reset - Proposal to put 50% of treasury funds into escrow

The DAO up until now has been paying mostly for labor.

The results are abysmal - Limited end user benefits. Limited effective marketing of the advancements that have come to market. A chain halt. SEC labeling dash a security. Almost complete loss of interest in Dash in the market.

Our network is run like a popularity contest or frankly at this point like a hostage-taking situation. DAOs need not be like this.

I propose that Dash takes 50% of its treasury budget and put it into escrow as a prize fund. These funds can be help by the trust until instructed by the network via a formalized treasury voting process to release to winners whom have produced delivery to the network of the requested services. Contractors can help evaluate prize bidders and prepare a voter guide for MNOs to make such votes.

This proposal addresses the sad state of affairs for Dash in a two-fold manner.

1) One of the main arguments that under-performers in the dash network and their apologists point to is the limited capital for funding. "You get what you pay for."

By effectively reducing the treasury payout every cycle by 50% we are reducing the amount of Dash sold every month. This reduction of sell pressure should rise the price every month. When the price increases, this will allow for the DAO to be able to finance more work with the same amount of Dash in the future.

If we can't force DAO fund recipients to product value to the network, we can certainly stop them from dumping on us.

2) Instead of paying for ineffective and structurally questionable network contractors, we should transition the funding system (at first only 50% and perhaps eventually 100%) to an outcome driven request for proposal (RFP) prize system. How to do this will be a question we can answer as the funds in the system accumulate.

The first RFP prize should be the completion of release 1 of the long awaited Dash Platform including whatever features are part of scope 1. In parallel with this, we must instruct DCG to open-source and make available all code and documentation that may as of yet be unpublished.

We can put all 50% of the sequestered funds into this Dash Evo prize bucket, until a process is developed on how to scope out additional RFPs.


To summarize.

1. We must stop the bleeding by cutting funding. Our current process has damaged the network by nearly every metric - price, reputation, vibrancy of the community. This funding should go into an outcome based prize fund initially for completion of Dash Evo release 1.

2. We optimize the Dash DAO spending on results not activities. A functional requirements and authentication process will need to be developed to spec out RFPs, evaluation criteria, and how the evaluations of bidders will be conducted. In an open-source world, these are surmountable problems.
 
@TheNetworkIsBiggerThanYou
The idea is good and I want to dedicate more time to think about it.
A question tho: in terms of the protocol software development - who would be responsible for the definition of the requirements, testing/quality check and then deployments?
 
Instead of paying for ineffective and structurally questionable network contractors, we should transition the funding system (at first only 50% and perhaps eventually 100%) to an outcome driven request for proposal (RFP) prize system.

Are we talking about possibly transferring the Dash Budget system into a system AKA the Dash Incubator ? (where developers can claim bounties, after having done the work)

How do you keep such a proposal prize system sufficiently decentralized ? Or in other words, how do you avoid centralization ?
 
Last edited:
What type of centralization do you have in mind?
Asking because you can't avoid centralization in every aspect of system lifecycle.
In the case of Dash Incubator there are only a few people (5?) making the decision to reward developers with the bounty for the tasks they performed. That is a form of centralization that i don't like to see in a budget system, that can possibly replace our current budget system.
 
@qwizzie I don't think you can avoid some centralization in every aspect of the system.
I don't see how decentralized network can be competent enough e.g. to prepare requirements, ensure technical feasibility, make quality/security checks of delivered products, or deployments and many, many others.

Theoretically, you could make an attempt to build such system, but it would be EXTREMELY complex and ineffective beyond imagination, as it would rely on the decentralized network to check and approve every step of the process.
It would also need to work, based on impossible assumption that decentralized network is competent in literally everything.
 
@TheNetworkIsBiggerThanYou
The idea is good and I want to dedicate more time to think about it.
A question tho: in terms of the protocol software development - who would be responsible for the definition of the requirements, testing/quality check and then deployments?
the remaining 50% is available for the network to hire contractors/firms.

Instead of electing "free" labor to guide the project like the decrepit trust protectors, the network can afford competent experts to guide the process.

It can be/ should be that each prize bucket has its own contractor set.

Ideally the contractors are stand-alone companies contracted specifically for this project.

In this way, there would be less centralization risk. If the contractors fail to properly scope out the project or fail in any other numerous ways, a) the damage will be limited to one prize pool and b) the network will have compelling alternatives to replace them.

On a side tangent, I believe the root cause of Dash's issues are that when a network is sufficiently decentralized the media (the person with microphone, the moderators of the platforms) have a disproportionate amount of power. People who seek these roles, generally speaking, are not the types of people you want leading. It is a de facto centralization force even if only informally. I don't know how to address this problem. As such, you can have a situation where the internal dash media proposes all sorts of prize funds that are counter productive and the MNOs can eat it up. So this is not a golden bullet solution as currently formulated.

To address this core problem, some sort of prediction market would be needed where unpopular but viable and important upgrades can happen to/within the network. Or perhaps something as simple as changing the success criteria for funding of these prizes. This way even a smallish minority of MNOs can fund what they think is needed, even when the majority are being persuaded by the over sized voice.
 
Back
Top