Hey @freak12techno thanks for chiming in. These are all valid points to consider.
Regardless of how many measures we can put in place, there’ll always be a certain level of trust required when it comes to funding teams working on the Hub from the CP.
Technically speaking, there is nothing stopping teams that received funds from the Community Pool once a clawback process of any kind is initiated. This is why the process to get funding from the CP is long in the first place: based on the proposal presented, the community will have to assess the team, the likelihood of them delivering on their promises and whether or not the amount asked is justifiable.
The intended tooling that we aim to introduce isn’t supposed to replace the key trust assumption of trusting the team to not steal funds, instead it builds on it to make the clawback process easier, automated and accessible to any community member.
We fully agree on this. For example, grants approved by AADAO are subject to milestones and deliverables to unlock the full amount approved, which could be tracked on AADAO’s dashboard for issued grants.
However, it’s true that this process requires a centralized entity to set, negotiate and approve milestones which makes it tricky to implement at the governance layer… This is why we, AADAO, are funding Binary Builders to build the DRIP module which will provide funding disbursement to teams linearly. As a result this will reduce sell pressure on $ATOM and enable governance to halt future funding.
Once fully developed, a proposal to implement the DRIP module will be posted on the forum.