A proposal to increase:
- BAL - supply cap
- SNX - supply and borrow cap
- LINK - supply cap
- MaticX - supply and borrow
The recommendations below were made utilizing Chaos’ supply and borrow cap methodologies and after analyzing user positions for each asset.
Please note that there are several other assets across V3 deployments with high supply and borrow cap utilization that were analyzed and do not have recommendations for an increase, given current market conditions. We maintain continuous monitoring of protocol usage and adjust our recommendations in response to evolving market conditions based on our simulations.
The supply cap for SNX on Ethereum V3 is currently at 98% utilization.
The recent increase in SNX supply is due to a single user supplying ~1.28M SNX, amounting to over 65% of the total SNX supply. The user is currently borrowing over 1.4M in stables against his SNX collateral.
Utilizing our supply cap methodology and given the debt ceiling set, we do not observe excess risk when increasing the supply cap for SNX on Ethereum. However, given the current concentration in a single user, we recommend a modest increase of the supply cap to 3M SNX.
The supply and borrow cap for BAL on Ethereum V3 are currently at 90% and 71% utilization.
Utilizing our supply cap methodology and given the debt ceiling set, we do not observe excess risk when increasing the supply cap for BAL on Ethereum. We recommend doubling the supply cap to 1.4M and the borrow cap to 370K
The supply cap for LINK on Arbitrum V3 is currently at 84% utilization.
Our methodology recommends capping the supply at 50% of the total circulating on-chain supply. With the circulating supply on Arbitrum at ~3.63M LINK, we recommend increasing the supply cap to 1.8M. Utilizing our supply cap methodology, we do not observe excess risk with this increase.
|Current Supply Cap
|Recommended Supply Cap
|Current Borrow Cap
|Recommended Borrow Cap
Once we receive feedback from @Gauntlet on the above recommendations, we will move forward to implement these updates via the Risk Steward process.
Chaos Labs has not been compensated by any third party for publishing this ARFC.
Copyright and related rights waived via CC0