6 replies, 471 views, 2 likes
The discussion focused on adjusting supply caps for rETH and LUSD on Arbitrum v3 and Ethereum v3 respectively, with Gauntlet suggesting increases due to high cap usage. The conversation concluded with the execution of the proposed cap updates, highlighting the importance of monitoring cap usage and making necessary adjustments for smooth platform operation.
The discussion primarily revolved around the adjustment of supply caps for rETH and LUSD on Arbitrum v3 and Ethereum v3 respectively. Gauntlet initiated the conversation by suggesting an increase in the rETH supply cap on Arbitrum v3 to 1700 and the LUSD supply cap on Ethereum v3 to 12m, citing high cap usage as the reason. They also recommended an increase in the rETH borrow cap on Arbitrum v3 to 340 due to its 94% usage 1,3.
ChaosLabs agreed with Gauntlet's recommendations but further proposed an increase of the rETH caps to 2,600 rETH 2,4. This suggestion, however, was not supported by Gauntlet who stated that their current methodology did not allow for such an increase in the rETH supply caps on Arbitrum at this time5.
The discussion concluded with the execution of the proposed cap updates via Risk Steward6. This indicates that the community agreed on the need to adjust the supply caps for rETH and LUSD on the respective platforms, although the proposed increase to 2,600 rETH was not implemented. The conversation underscores the importance of monitoring cap usage and making necessary adjustments to ensure the smooth operation of the platforms.
Posted 4 months ago
Last reply 3 months ago
Summary updated 2 months ago
Last updated 08/12 04:39