Following the timeline, we have created an ARFC Snapshot for the Aave governance to vote on a follow-up distribution described in the previous post.
To keep the transparency with the community, we would like to clarify different points:
- Both us and Chaos Labs are technical service providers of the DAO, and as such, during this thread we have tried to do an objective analysis of the situation and provide a recommended solution, with this topic being top on the list of priorities. During these past 4 months, we have tried to be as transparent as possible and, at the same time explain our reasoning in what we think is a clear manner for everybody on this forum.
- Any proposed resolution has a time component associated: no matter the model, aAMPL holders should receive funds as soon as possible, and also all different models introduce compensation until exactly when the funds are claimable.
Not doing any type of proposal is not an option, as it would lead to further problems for users of AMPL on Aave, the Aave DAO and Ampleforth. - Aave is an open governance on which any participant has the right to submit proposals, and the DAO has mechanisms like the Skywards program by @ACI which allows entities not having AAVE power to get their proposals submitted.
This means that if anybody simply doesn’t agree with our proposal, it is possible to go through that route and pursue an additional proposal, after our final proposed distribution. - After this proposal, from both our professional service providers engagement (BGD Labs and Chaos Labs), we are open to support any additional proposal by any other party, but only when fully approved by our customer (the Aave DAO) via the standard Aave governance procedures, and always if falling within the terms of our respective agreements.