The community already implemented a procedure, why do we need an extra step?
1 Like
No need for this extra step!
1 Like
Vote could be activated only if there’s Community disagreement. This will ensure layer of oversight when needed.
I think this is invalid and could potentially hamper and overcomplicate the community elected system of checks and balances that should be in place for the grant system. It shouldn’t just be based on who can lobby and whale enough votes to pass something through, and a standard should be established with some individuals who are able to help regulate the grants. Sure it’s decentralized, but the decentralized community recently voted this committee and its members in place. They should have more time to work before something like this should even be considered.
1 Like
In reality, the Community already has the ability to revoke grants through the DAO governance process, as evidenced by past precedents. This proposal doesn’t seek to undermine the Committee, but rather to ensure the Community’s voice in significant decisions and to refine procedures, providing an avenue for disagreement with Committee and establishing a protocol for such situations.
Decentralized governance does not mean that everyone has to decide on everything. It means (among other things) that the community can easily and in a permissionless fashion give and take back power from representatives, delegates, or organizations making certain decisions. In the case of grants, I do not have time to conduct a thorough review of a questioned project to determine if it should be revoked or not. That’s why we elected a committee that can acquire sufficient context and spend time understanding the situation before making an informed decision. The great thing is that if I do not trust the committee or any of its members, I can create a Hiring/Firing proposal and replace their members, or I can initiate the governance process to change the structure or dissolve the committee.
2 Likes
This is a nice conversation by the way.
My own opinion is telling me that this kind of power of DAO Committee dishonours the DAO’s decision on approving a Grant regardless whether the Grantee is doing it right or wrong.
Let the community review again, in tandem with GSS or any other squad, regarding any revocation request before the DAO Committee executes any pause or revocation.
If a whale approves a Grant, it’s okay because she owns the governance token and voiced only her decision. If you will invalidate her decision, that means you are dishonouring her purpose of holding the governance token.
We can make it right by letting them participate on the revocation process before pausing or revoking any given grants.
Another way is to tag them (those who voted Yes) to personally participate in the review process.
Just my personal opinion mates. I do not intend to change any process.
1 Like
Is this part of your work as the StrategicUnit?
Thanks for the clarification, Lord. I truly don’t think this is necessary. If we need to community-vote everything, why are we delegating decision-making and giving autonomy to teams that have broader context?. With this framework, each feature that DCL Foundation wants to build should go through community voting first, even if we as a community delegated them with the power and responsibility to execute on the product roadmap of the project.
Hi Gino, thanks for your feedback. While the Community delegates certain decision-making responsibilities to Squads/Committees with specific expertise to maintain the DAO and move towards achieving its goals and mission, it’s also important to remember that the Community plays a crucial role in the DAO’s governance process.
The DAO has already been involved in the process of enacting grants, so it seems consistent to also involve it in the revocation process when necessary. This doesn’t mean that every decision will need to go through a vote, but rather that the option is there should the need arise.
The number of grants that have been revoked is relatively small compared to those funded - 13 out of 178 (≈ 7%). As I mentioned earlier, a Community vote can be activated only if there’s disagreement with the Committee’s decision, so the extra time needed for the process in these cases would be manageable.
This proposal is about ensuring that the Community has a voice in significant decisions, enhancing transparency, and aligning the process with the values of Decentralization. I hope this clarifies the intent behind the proposal.
Also, this proposal concerns only the DCL DAO grants revocation process. The Decentraland Foundation is separate from the DAO, and I agree that the delegation framework should consider certain specifics like time optimization, certain autonomy when dealing with feature development, but I also think that some features should be discussed with the Community.
As to original Decentraland white paper:
“Unlike other virtual worlds and social networks, Decentraland is not controlled by a centralized organization. There is no single agent with the power to modify the rules of the software, contents of land, economics of the currency, or prevent others from accessing the world.”
I never agreed with the formation of yet another committee and more money spent on something the GSS was already doing with support from the community. However, we just elected them and I think we should allow this community-wide decision, which took time and arduous work to implement, a chance to function before changing the process yet again. The community already has the ability to revoke a grant by way of the governance process if there is an immediate need to. This would be unnecessary.
Hi, thanks for your feedback. This proposal aims to streamline the grant revocation process by aligning it with the existing governance process opportunities. This will empower the Community to act more efficiently by envisaging such cases and creating a protocol for them, thereby reducing the time and complexity involved in making these important decisions.
Seems like you should spend more time working on what the grant you got is paying you to do and less time trying to figure out how to hold onto that grant without actually working on it.
Should the Community Be the Final Arbiter in Grants Revocation Decisions ?
This proposal is now in status: FINISHED.
Voting Results:
- Yes 55% 5,916,057 VP (38 votes)
- No 1% 13,020 VP (14 votes)
- Invalid question/options 44% 4,746,309 VP (49 votes)
This Prop is silly, why would we want to leave the decision to revoke grants up to @RobL sounds counter productive to me 
1 Like
Hey, now there is more than 12 million VP in circulation only delegated by Esteban, so the decisions will be up to the Community.
Should the Community Be the Final Arbiter in Grants Revocation Decisions ?
This proposal has been PASSED by a DAO Committee Member (0xbef99f5f55cf7cdb3a70998c57061b7e1386a9b0)