I think this is a perfect example of the type of task that should be delegated vs. directly managed by all members of the DAO. I was on the dev call for the discussion last Saturday and the entire team spending time weighing the merits of various lending protocols seems like a misallocation of valuable team resources.
We are talking about allocating max $60mm of capital to mostly stables so this is $3-6mm in annual income (5-10% APR). That is nontrivial and I am 100% in favor of deploying the fund but treasury strategy will have a miniscule impact on Mango’s ultimate success.
We have so many bigger challenges to overcome and cool product improvements we can make. Having our leadership and overworked dev team focus on the treasury feels misguided.
I believe this should be a two-person execution effort with voting approval required by the DAO. Someone with spare capacity compiles a report with objective pro’s/con’s of various investment options including stable lending projects on SOL, non-stable assets (BTC, ETC, SOL) and structured option vaults.
Lending project criteria include: (i) security evaluation (open source, audit, TVL, has Mango team reviewed the code), (ii) yield estimates, (iii) team openness to our investment, (iv) historical collaboration with Mango and (v) other criteria as relevant.
The second member of the treasury team would be a senior Mango contributor and assist with any issues associated with the report preparation. The draft report would include proposed allocations of the insurance fund across the lending pools, non-stable investments and option vaults.
Upon completion, a draft of the report will be published on the forum for a two-week comment period. These comments are then incorporated by the Treasury team. A final recommendation is published and subsequently put up for a DAO vote. The DAO vote will determine whether the allocation should occur as outlined by the report.
In my opinion, this approach optimizes for (i) near-term insurance fund deployment, (ii) rigorous due diligence on allocation options and (iii) minimal distraction for core team members. This is also a good test exercise for how Mango can leverage committees to execute more projects in parallel.