ARC - Greenlight Aave Sagl (the company) to do certain types of changes without having to go through the AIP process

Technically speaking, the next update of the protocol would have the ability to delegate votes to other addresses. This means that anyone can delegate to whom they might fit to vote on their behalf. That is something that can help technically if such objectives are required.

Currently the Aave Protocol is open-source and runs autonomously on Ethereum. If there is any significant changes, these should go trough governance decision making especially if it involves incentives. It’s important that there is wide decentralization and mandate to cover this decision making by the token holders as they are end of the day bearing the risk of the protocol.

However, governance does not need to be slow or inefficient, this means that there should be many various topics open for discussions and those topics that are more progressed could progress to a formal proposal accordingly to the AIP framework.

What could be important is to set different kind of minimum thresholds of various voting topics such as assets listings, small protocol upgrades in the future and incentives changes, for example what would the minimum voting period be set. This might provide the needed flexibility to AIPs and their progresses.

One of the things that takes time is usually configuring the payload to correspond the execution of a voting outcome or might be an external factor (for example in case of listing AAVE, the price feeds by Chainlink was recently set as the asset was available on multiple market venues).

I guess the bigger question of this thread is as @Laur pointed out: what kind of actions or ideas we could come up with to keep the agile progress on AIPs without compromising the security/diligence of code deployment and ensuring that there is due process in voting. Would definitely like to hear more opinions on this topic.

This topic is especially important since I would imagine in the future that there are multiple different stakeholders participating in the risk assessment of the protocol assets, contributing to the codebase and other works as well.

6 Likes