As it’s a proposal that got additional discussions, here’s StableLab’s voting and rationale on Uniswap Unleashed.
Voted: Abstain
Regarding this proposal, we had several discussions and we thank everyone including Uniswap Foundation members and other delegates for their opinions. We focused on questions regarding assessment criteria and three aspects for our voting decision.
Whether the proposal should been seen under the different assessment criteria
-The Uniswap Foundation is a steward for Uniswap DAO, which was voted in by DAO vote, and it holds interest and information distinct from other working groups or service providers to Uniswap DAO. For example, legal challenge to Uniswap DAO impacts its participants but the Uniswap Foundation is likely to face bigger challenges compared to others. Several members of the Uniswap Foundation have been contributing to the Uniswap ecosystem before the Foundation’s creation, and their concerns for the ecosystem, driven by both reputation and personal interests (financial and otherwise) are reasonably greater than other Uniswap DAO participants. However, as StableLab recognizes, this is subjective and sets a precedent that could be misguided, so we decided to evaluate the proposal under the usual assessment criteria. Three aspects were evaluated: scope, budget, and impacts.
Scope
-The scope of the proposal is extensive, covering operational cost, marketing, and large grants budgets for research and governance. The Uniswap Foundation has the mandate to request these, as it also has the ability to request funding grants and also distribute it to grantees it decides. We understand the concerns from other DAO participants that new scopes have been created and initiated by the Foundation including Unichain. But for this, as the mandate given to the Uniswap Foundation also covers the ever changing nature of DeFi, we believe that the scope is still valid.
Budget & Impacts
-There are two main compositions of the budget: operational and grants. Regarding the operational budget, while it might be controversial to note, we don’t think it’s necessarily unreasonable. For larger DeFi DAOs like the Sky ecosystem, costs have been around $150 million USD over the past 12 months. Granted, Sky makes sustainable and strong revenue. However, considering Uniswap is a protocol with over $4 billion USD in TVL and market cap above $4.8 billion USD, presence of the Uniswap Foundation was able to generate or defend more than $20 million USD per year in TVL and marketcap is reasonable. This is especially valid in potential extreme situations such as hacks or governance attacks, where the presence of the Foundation helps to coordinate defense, mitigating coordination issues. Therefore, the operations budget is valid.
-The grants budget, which is more than double the budget for Operations, is contentious due to the budget size and question regarding its impacts. While we appreciate the report, such as this, aside from grants spent on audits, which are understandably important, it’s difficult to see actual impacts. For example, the report noted over 400+ new hook developers, which is great, but how much TVL and revenue will they generate? A big portion of the grants are ongoing, we don’t necessarily believe that it would be beneficial to create more burdens for the Foundation team with larger grants to manage. This is also considering there are already large grants specifically for Unichain and V4 migration (which we suggest just incentivizing v4 onboarding to Unichain.)
Suggestion
We strongly recommend the Uniswap Foundation to reconsider how it wants to move forward with grants. One approach could be for the Foundation to present a monthly or quarterly list of grants for DAO approval, with comments explaining the recommendations. Alternatively, a more narrow list and budget for grants might be considered.
Conclusion
Traditionally, Uniswap Governance utilizes Snapshot (offchain voting) for sentiment, allowing onchain proposals to incorporate more details or edits as needed. We voted to abstain at this time, anticipating that the outlined concerns will be addressed in future iterations.