Improve permissions management on Aave v2 and define a better strategy for access control roles on Aave v3

Hello Aave governance members,

I put together a proposal some time ago regarding a risk committee for the SNX DAO (which can be viewed here SIPs/sip-273.md at master · Synthetixio/SIPs · GitHub), and have viewed the discussion in this thread and would like to share some of my thoughts regarding the concept of a ‘risk committee’.

The problem space highlighted by OP involves the Aave protocol having the capability to make ‘faster’ changes to parameters in order to respond to rapidly changing ecosystem changes. This in itself is a worthy goal, however it should be noted that this is a different in essence to risk and it’s management.

I think what OP is really trying to describe is a organisational group that is empowered to react to changing ecosystems, where those changes are within a subset of the Aave risk appetite.

The topic of a risk committee, whos primary focus would be the development and application of a risk framework is a separate problem spaces which requires thorough consideration independently of the use case that OP, as its scope is much broader and implications further reaching.