As some will already know, TokenLogic voted NAY on the TEMP CHECK and the below explains why we will be voting NAY on the [ARFC] Snapshot.
Firstly, similar to BGD’s comments, we do not see much value in this proposal given the fallback oracle would only be called if a Chainlink feed returns a negative or zero value. However, with the minimum threshold for Chainlink feeds configured to ensure a positive value above zero is returned, we don’t see a situation where the fallback would ever be called.
While we believe oracle security is extremely important to Aave’s robustness, we don’t believe this proposal provides any additional meaningful improvement over how Aave currently operates today but in fact, introduces additional resources to be accounted for. For example, while the proposal offers a grant to cover the costs of publishing Pyth data on Optimism for three months, it’s unclear who’s expected to cover the costs after this period and if this responsibility will fall to the DAO. We don’t see the benefit in spending valuable time and resources to do the integration work only to pay later for something that won’t be used.
Secondly, we have some general concerns around Pyth’s incentive design as an oracle provider, specifically their close ties with historically predatory and opaque market makers, such as Alameda/FTX and Jump. These relationships pose a clear conflict of interest, where the entities reporting the market price of crypto assets are also actively involved with crypto market trading activity and therefore could be profit-motivated against the interests of Aave users.