Responding factually to each of your points:
CRV AIP
AIP 146 was executed successfully, allowing the acquisition of 2.7m units of CRV, clearing the remaining excess debt on Aave V2. We wrote in detail the steps involved in the CRV proposal here; there were a number of steps and each was significantly complex. It is important that we allowed enough time for contracts to be developed, peer-reviewed internally, and peer-reviewed by BGD. Specific price movements are out of anyone’s control. It is not in Aave’s best interest to compromise on security for the sake of speed. The CRV Bad Debt Repayment Contract involved multiple moving parts, with external system dependencies and validations. The proposal payload involved the following:
- Converted the existing USDC balance within the Aave v2 Collector contract to aUSDC so that it was not sitting idle in the treasury.
- Approved the CRV Bad Debt Repayment Contract to spend up to the aUSDC Cap defined in the CRV Bad Debt Repayment Contract from the Aave v2 Collector contract. This was required to enable the CRV purchase.
- Approved the CRV Bad Debt Repayment Contract to spend up to the CRV Cap defined in the CRV Bad Debt Repayment Contract from the Aave v2 Collector contract. This was required to pay back the CRV bad debt on behalf of Aave.
Charged for consulting to third-parties around Aave, for example teams looking for asset listings
During our Aave contract, we never received payments from external parties for asset listings. Before our contract, we helped Lido and Stader with the engineering work required for asset listing proposals and we were paid a small amount. This was encouraged by Aave Companies and others because asset listings require protocol expertise.
they failed to ensure the collector contract had sufficient aUSDC balance
Our payload to increase aUSDC on mainnet has been with BGD for review; it will be live as soon as it is approved. We have periodically updated Certora and other groups about this payload.