In my opinion, the community snapshot is a waste of time for all involved.
The current order is: MALF- snapshot - Gauntlet assessment - Formal proposal - listing
Most of these snapshots end up passing quorum, but then disappear if Gauntlet does not recommend. I think it would be important to provide the Gauntlet assessment with or even previous to the snapshot. This way the community can make a better informed decision.
I don’t think Gauntlet’s “recommendation” should supersede a community vote days/weeks later. Now I know a lot of you will call snapshot a “heat check”, but it is a community vote that requires quorum. Otherwise, it’s pointless.
I have heard the argument that this new order would cause undue burden on Gauntlet, but they end up doing an assessment on snapshots that pass anyway. A solution to this could be that the applicant is required to pay Gauntlet for a “pre-assessment”. Then the pre-assessment could be provided with the snapshot so we can make more informed decisions.
**New revenue stream for Gauntlet..
Some examples:
IDRX did not have an oracle. This should never have made it to snapshot. Some MALF requirements should mandatory before proceeding to snapshot.
eUSDC the community voted for it (passed), days later the Gauntlet assessment stated eUSDC as a security risk. The End? The same with AVAIL. Does the buck stop with Gauntlet, or is it a recommendation?
VVV the community voted for it (passed), days later Gauntlet *suggested against it, but stated that if the community voted to proceed, here are suggested perimeters. Did the community not vote to proceed? I think they did… if not, then how?
I would also suggest Gauntlet be more consistent in their recommendation summaries. (VVV vs. eUSDC please review the first three paragraphs) are you flat out telling the community No, or, are you recommending no? If the latter, how do we proceed in determining the answer?
Final point.
I think I if we just reordered the processes it works better for all. I also think we have an opportunity to streamline the process. What if the Gauntlet pre-assessment was a “recommend”? Maybe the incentive could be to skip the snapshot and go straight to formal proposal. If Gauntlet is a “not recommend”, it goes to snapshot with the assessment.
The risk to the “not recommend” is that the community approves in snapshot. But at least you’ve given us the full information to decide, and Gauntlet has provided tight perimeter recommendations to help secure. You could also adjust snapshot quorum, or create a system where only delegates vote on snapshots. Lots of options here if you’re worried about community risk.