Because USDe, sUSDe, and their derivatives(eusde pusde..) already account for the majority of Euler’s supply, a significant price fluctuation for USDe would be devastating to Euler. We recommend following AAVE’s lead and hard-coding the USDT oracle for USDe. AAVE has already discussed the reasons in detail; please refer to their discussion[ARFC] sUSDe and USDe Price Feed Update - Governance - Aave
2 Likes
Thanks for the feedback, will pass onto the risk curators and get their thoughts.
1 Like
the majority of looping assets is USDC in Euler yield.
No matter hard code it into USDC/USDT, or keep the current 1 for PT-USDe, will not help much in the event of Ethena collapse.
Probably some real time monitoring and reactions from Euler protocol can mitigate some damages in this scenario.
Personally I have withdrawn all borrowed assets against PT Usde to stay safe.
Still, would like to see more innovative ways to deal with the Usde, especially in the event that Usde collapse.
1 Like
The reason for hard-coding this is not to prevent Ethena from crashing, but rather to prevent extreme market fluctuations that are unnecessary but can have a devastating impact on Euler. The reasons for this are detailed in the AAVE forum, which you can check out.
1 Like
The situation 4 hours ago fully verified that my suggestion was correct. USDE on AAVE was completely unaffected, and USDE quickly restored its anchor. However, with the market pricing oracle on Euler, many people who collateral USDE (PT) to borrow USDT (USDC) will be liquidated.
Binance has already announced that it will set a lower limit on the price of USDE, and AAVE directly pegs USDE to USDT. Euler should learn from them.