BolehVPN
Well-known member
I'll confine my two cents to the budget system and not on Transform PR which I'm right now on the fence:
I did post about this in a separate thread but I'll post it here again:
- I am for the proposal and contract system with the contracts having a higher threshold.
- I agree that contracts should not be for absurdly long times and should have a limit of 12 months for the moment.
- There has to be ability for an exit vote where a contract that is not performing well or defaulting can be stopped. This is critical. Even in commercial contracts. This can be achieved either through No votes (which requires a higher threshold) or the proposer cancelling it or a combination of both. One way is to have it as follows, if proposer puts in the cancellation request, a lower threshold of votes is required but if the proposer doesn't, then a higher threshold is required. Especially when it's most likely the proposer that is entering into the contract with the third party (see below), the proposer should be given a bit more say in cancelling a contract.
- Would be interesting to know who is the person that is entering into contracts with third parties right now.
I did post about this in a separate thread but I'll post it here again:
Well Dash itself does not have a separate legal entity unless you use the Dash Foundation but I don't think this is the right entity for this since masternode voters are not always Dash Foundation members. The Dash Foundation is more about promoting Dash interests rather than controlling the budget.
Strictly speaking, the contract should be between Dash masternode owners and the Vendor but we have to realize that Evan does not have the authority to bind the rest of the Dash voters unless given authority from the masternode owners nor is it ideal for him to be able to do so. The Dash dev team in their individual capacities can be bound but a clause should be inserted in their contracts that it is always subject to the voting mechanism and fernando should be on top of it. This allows a vendor to enter into contract with somebody and have some legal certainty on the terms but yet also have something in place if the vote turns the other way since that is out of the Dash dev's control. However if the voting mechanisms are changed halfway through the contract, we have to think what happens then.
Strictly speaking, the contract should be between Dash masternode owners and the Vendor but we have to realize that Evan does not have the authority to bind the rest of the Dash voters unless given authority from the masternode owners nor is it ideal for him to be able to do so. The Dash dev team in their individual capacities can be bound but a clause should be inserted in their contracts that it is always subject to the voting mechanism and fernando should be on top of it. This allows a vendor to enter into contract with somebody and have some legal certainty on the terms but yet also have something in place if the vote turns the other way since that is out of the Dash dev's control. However if the voting mechanisms are changed halfway through the contract, we have to think what happens then.