Summary
A proposal to:
- Increase weETH’s supply cap on Aave’s Ethereum deployment.
- Increase GNO’s borrow cap on Aave’s Gnosis deployment.
Motivation
weETH (Ethereum)
weETH has reached 100% supply cap utilization on Ethereum, and its borrow cap is at 27% capacity.
Supply Distribution
All top suppliers of weETH are looping the asset, either with WETH or itself. Thus, these positions pose little risk of liquidations, given weETH’s calculated oracle.
Overall, ETH-correlated assets represent over 99% of the value borrowed against weETH.
The primary blocker to increasing weETH’s supply cap has been WETH utilization. However, we have observed a decrease in utilization recently, driven by rapidly increasing WETH supply. Thus, there is now enough borrowable WETH below UOptimal to recommend increasing weETH’s supply cap.
Recommendation
Given on-chain liquidity, user behavior, and WETH’s utilization, we recommend increasing the weETH supply cap.
GNO (Gnosis)
GNO has reached 67% supply cap utilization on Gnosis, and its borrow cap is at 98% capacity.
Supply Distribution
The two largest GNO suppliers represent 44% and 37% of total supply, respectively, with the larger of the two holding a health score of 1.76, while the smaller maintains a deposit-only position.
This market is in isolation mode, thus the only assets borrowed against the supply are USDC and WXADAI.
Borrow Distribution
The top borrower of GNO represents 44% of the total amount borrowed, with the second largest representing 23% of the total. Both positions primarily use wstETH as collateral.
In aggregate, wstETH represents 64.9% of the value backing GNO loans.
Recommendation
Given on-chain liquidity and user behavior, we recommend increasing the borrow cap by 2.1K GNO.
Specification
Chain | Asset | Current Supply Cap | Rec. Supply Cap | Current Borrow Cap | Rec. Borrow Cap |
---|---|---|---|---|---|
Ethereum | weETH | 660,000 | 720,000 | 200,000 | - |
Gnosis | GNO | 60,000 | - | 4,400 | 6,500 |
Next Steps
We will move forward and implement these updates via the Risk Steward process.
For transparency, we aim to execute the risk steward transaction on August 9th at 16:00 pm GMT
Disclaimer
Chaos Labs has not been compensated by any third party for publishing this ARFC.
Copyright
Copyright and related rights waived via CC0