The discussion primarily revolved around Gauntlet's expansion of its simulation platform to provide continuous market risk management for Aave’s V3 markets, starting with V3 AVAX and then V3 ETH. This move was in response to the community's demand for market risk management for other markets, with a focus on the largest markets first to drive the most impact. Gauntlet's risk modeling for Aave V3 includes managing risk across chains, modeling different token and market metrics, and analyzing their implications on user behavior and protocol impact. They are also building infrastructure to support new features in V3 such as efficiency mode, new risk parameters, isolation mode, portal, siloed borrowing, new governance controls, and risk admin role.

Pauljlei outlined the major integration milestones for V3 AVAX, including smart contract integration, ETL pipelines, model development, dashboard development, and model QA. The first set of parameter recommendations is targeted for early October. Gauntlet is also working on V3 Ethereum integration and will keep the community updated on their progress¹. AndrewA raised concerns about potential data quality issues, mentioning that some grant applicants have encountered problems with Aave subgraphs². Inkyamze responded that subgraphs are generally unreliable and that Gauntlet has developed its own internal infrastructure for ongoing risk management ^3,6. AndrewA suggested that Gauntlet could open source some of their infrastructure or maintained resources, which could be valuable to the ecosystem⁵. He also proposed gauging demand for multi-chain, V3 data and starting a dialogue about what data pipelines Gauntlet is building⁷.

Yonatan, CTO of Chaos Labs, disagreed with the statement that subgraphs are unreliable. He explained that they use multiple data sources for redundancy and reliability, and that errors in subgraph data validity are likely due to errors in collection logic and data parsing. He highlighted the benefits of open source data collection frameworks like subgraphs, including community transparency⁸. Yonatan mentioned that since the release of the v3 Risk Application, there have been numerous inquiries about data availability and integrity for v3. They expressed willingness to participate in any initiatives to make this data more accessible to the community. They suggested starting with subgraphs, due to their wide adoption, but are also open to other ideas or proposals⁸.