To submit a proposal to the DAO, you do not need a TMP. You may begin with a Discussion and progress to a snapshot vote. As far as governance and fund protection are concerned, the Risk Officer has no role to play. I’ll explain again with an example to make this more clear.
Let’s say I am Jeff, a scammer, and I am aware of the flaws in Wonderland’s system. I see a few big players redemeeting next month. It is likely to take a week or two to accumulate sufficient voting power to lock snapshot voting. Then I can initiate a discussion about investing in this seed stage of my project with, for example, 10 million dollars. The first step I take is to make sure that I have multiple bot accounts in order to secure my Discourse campaign, and then with my voting power I will secure the snapshot voting process.
We need a management team that is capable of assessing and blocking malicious actors and will approach all new ideas with caution. There may be an argument that for every point I am making there is also another solution, such as improving our governance. There is always more than one solution to every problem. Here is my proposal to address all these issues, and hopefully it will be only the first step towards improving every aspect of this organization.
I agree with you that TMP’s should never have existed in the first place and the Team is responsible for that. Moving forward, we must assess all aspects of any proposals to come, both positive and negative, in order to avoid repeating the same mistakes.
The purpose of this proposal is not to address a single issue.
As a matter of fact, regardless of whether Sifu holds an official position with Wonderland or not, he is always available to provide insight and advice. Is there any reason why he should not be given an official position, recognized for his contributions, and acknowledged for his valuable contributions since Wonderland benefits constantly from that?
According to your argument, since Sifu will remain around regardless, should we exploit this habbit and continue to benefit from his advice, while keeping him out of our official structure? I do not understand that, and in a sense, I find it offensive. To me, it makes sense to engage with anybody who is willing to provide assistance where Wonderland requires assistance. If Wonderland needed marketing assistance, I would include you in the proposal without a doubt. As Wonderland requires guidance and advice, Sifu has been included.
The voting process of the DAO should, in ideal circumstances, address only the most important things and decisions. All investors should be aware that every time we issue a call for action, this call needs to be addressed. It would have been difficult for me to keep up with the voting process if I were not working for the Wonderland DAO. Investing in Wonderland should not be considered a full time job, rather a passive income opportunity where you are receiving frequent reports regarding the fund’s performance and when action is required, you should take part in it because it is critical.
As of right now, we are providing tools for passive income, such as revenue sharing and active portfolio management by the DAO, but we are also asking for increased participation. There is a possibility that our investors would engage in the market themselves if they desired daily participation.
I am not invalidating the current governance, rather I am giving it a guidance aspect that we will follow to a certain extent while continuously striving to improve every aspect.
I am very disappointed if you imply that I drafted a large proposal solely for the purpose of redefining a position and sneaking in Sifu. I have explained in detail why Wonderland needs Sifu and I am very confident about that.
Again, I propose reforming the Wonderland DAO to improve its efficiency, security, and effectiveness. As a result, Wonderland will cease being sidetracked and refocus on providing profits for its token holders.
The main topic of a proposal to reform the whole DAO should not be Sifu, however, he is again the central subject of discussion. Sifu is proposed to fill a necessary role, nothing more or less.
Due to the drastic nature of this proposal, it is being started as a DD. During the RFC stage, I will refer to many of the points raised during this discussion.
I will be bold about this point with the confidence of following legal advice on this one. As per legal advice, for multiple reasons while managing any aspect of a fund of this size you need to make sure the management is compensated enough to eliminate the risk of any forms of bribery. It was suggested to follow the industries standards of “Two and Twenty”.
Edit: The management fee is covering all management expenses.
Two and twenty (or “2 and 20”) is a fee arrangement that is standard in the hedge fund industry and is also common in venture capital and private equity. Hedge fund management companies typically charge clients both a management and a performance fee. “Two” means 2% of assets under management (AUM), and refers to the annual management fee charged by the hedge fund for managing assets. “Twenty” refers to the standard performance or incentive fee of 20% of profits made by the fund above a certain predefined benchmark.
In this proposal I’m referring only to the two percent while I’m not including the Treasury Team.
My job is not to manage the Treasury Ser.
There will be many more steps to be taken after this proposal. With the approval of this proposal, we will dynamically define budgets for each expense of the DAO, and these budgets will be communicated frequently to token holders through the Treasury Reports.
The management fee is the compensation instituted to the management team.
In my opinion, the Team lacks the experience necessary to manage a multimillion dollar fund in a secure and efficient manner. Sifu’s contribution is necessary not only to identify the risks of possible financial investments, but also to all other aspects of the organization.
In my proposal, I state that a detailed report will be provided within a month for every position and the tasks they are assigned. As new requirements arise, this process will also be dynamic. The delegation of tasks should be done dynamically, rather than sending a new proposal every time a change occurs to redefine a role.
Please refer to my reply above to Gonzo.