According to ME News, on December 24th (UTC+8), monetsupply.eth, Spark's Head of Strategy, posted on X, stating that many people lack the necessary background understanding of the current Aave situation. Over the past few years, Avara and Aave Labs have been pushing forward the development of Aave v4 (funded by a $15 million grant from the DAO); simultaneously, ACI, BGD, TokenLogic, LlamaRisk, and other service providers (SPs) and the DAO have focused their efforts on expanding and growing Aave v3. During this period, Aave v3 grew into the largest on-chain lending protocol and also became a significant cash cow project (generating tens of millions of dollars in net annual revenue). From any perspective, the efforts made by the DAO and service providers around v3 can be considered a huge success. In contrast, during the development of Avara v4, a considerable portion of its energy was devoted to projects or acquisitions not directly related to the Aave ecosystem, and these attempts ultimately failed to bring incremental value to the Aave ecosystem. This has led to some disagreement regarding the future development direction of the Aave protocol, primarily concerning two paths: one is a full-fledged focus on migrating to v4 and effectively beginning to phase out v3; the other is to allow v3 and v4 to run in parallel for a long period, while continuing to support v3 for an extended time. Aave Labs leans towards the first option, while ACI, BGD, and other service providers generally prefer the second. Against this backdrop, control over the Aave brand and IP, especially the aave.com frontend, becomes particularly crucial. This frontend is currently the most important and widely used entry point for users to access the Aave protocol. This is not only about the fees generated by the frontend redemption function, but also about who controls the "traffic entrance" to the Aave ecosystem and ultimately, what v3/v4 development path will be adopted. (Source: ME)