This proposal aims to fix inconsistent / suboptimal configurations across various pools.
When Aave v3.2 went live, the existing eModes were just migrated to liquid eModes. What this means that if an asset was flagged as e.g. eMode 1 on v3.2 it was enabled as borrowable and as collateral on eMode 1.
This was done to not disrupt existing positions and also to isolate the upgrade from any configuration changes.
As some time has passed now, it is a good idea to disable unintended eMode configurations, namely we propose to:
This will not have any effects on existing positions, but will prevent increased borrows of the disabled assets within the eMode.
Some assets that were originally listed as borrowable have later been "disabled" by setting their borrowCap to 1 via risk stewards. While this workaround suits the needs, the "correct" thing to do, is to disable borrowing. Therefore this proposal permanently disables borrowing for:
In aip 261 the rates for v2 assets were aligned to standardize interest rates. This resulted in some unintended increase in interest rate on renFil, which has close to zero secondary market liquidity and thus makes it almost impossible for borrowers to repay their debt. Therefore we recommend reverting to the previous ZeroInterestRateStrategy to cut growth.
The proposal uses the config engine to implemented the described changes.
| description | borrowable before | borrowable after | | -- | |
In addition it calls to revert the interest rate on Aave V2 Ethereum:
AaveV2Ethereum.POOL_CONFIGURATOR.setReserveInterestRateStrategyAddress(
AaveV2EthereumAssets.renFIL_UNDERLYING,
0x311C866D55456e465e314A3E9830276B438A73f0
);
Copyright and related rights waived via CC0.
https://app.aave.com/governance/v3/proposal/?proposalId=313