Unresolved concerns

• Whether reducing liquidation thresholds on USDC and DAI is necessary and, if so, what magnitude of reduction balances risk mitigation against user liquidations.— eboado, omergoldberg, yaron
• Unclear what the community's actual risk tolerance and security budget should be for tail assets going forward, which should guide parameter decisions.— tarun, Alex_BertoG
• Whether disabling borrowing (less conservative) versus freezing (more conservative) is the appropriate response, given disagreement among risk providers and the DAO.— eboado, Llamaxyz, Callen_Wintermute
• Lack of clear timeline for V3 Ethereum deployment, making it uncertain how long V2 assets will remain frozen and whether migration incentives will work.— fig

Notable participants

• PauljleiGauntlet risk analyst who proposed the initial freeze of 17 long-tail assets and provided detailed risk rationale throughout discussion.
• eboadoBGD contributor who provided detailed asset-by-asset risk analysis and pushed back against the blanket freeze, advocating for more granular parameter adjustments.
• tarunGauntlet principal who clarified the security budget framework and justified the freeze as preferable to across-the-board LT reductions on major assets.
• LlamaxyzRisk provider who acknowledged over-conservatism in the initial proposal and led effort to develop an alternative 'disable borrowing' proposal as middle ground.
• omergoldbergChaos Labs analyst who quantified liquidation impacts of LT reductions and proposed consensus parameters to disable borrowing instead of freezing.
• MarcZellerAave core contributor who supported the proposal as conservative risk mitigation and opportunity to encourage V3 adoption.
• monet-supplyCommunity risk analyst who identified specific stablecoins (GUSD, USDP, LUSD) with strong peg mechanisms that may not warrant freezing.
• AaveLabsCore team that signaled support for community-led risk response following the CRV incident.
• staniAave co-founder who ultimately voted for the freeze proposals while acknowledging merit in a more granular alternative approach.
• bgdlabsBGD team that provided technical clarity on V3 deployment timeline and governance proposal execution mechanics.