When questions began swirling across social channels about whether Aave’s latest upgrade would force users and integrations off the current stack, Kolten, Aave Labs’ Marketing Director for DeFi, sought to put doubts to rest. In a measured thread on X, he laid out the company’s position that Aave V3 will continue to operate “for the foreseeable future,” even after V4 lands, and there is “no rush” to deprecate the existing version.
The post reads like a careful reassurance to the protocol’s large ecosystem of builders, integrators and institutional partners, some of whom have voiced concern that a hard pivot to V4 could disrupt operations built on top of V3. Kolten emphasized that the timeline in the so-called “Aave Will Win” framework is intentionally flexible, not a firm deadline, and that Aave Labs will weigh “a lot of factors.”
It is the same kind of prudence expected when introducing any major DeFi protocol change. That message echoes discussions already unfolding in governance threads, where members have debated how and when V4 should be adopted without harming current markets. Aave Labs framed V4 as the culmination of nearly a decade of iterative protocol work rather than a sudden reinvention.
Kolten pointed to the team’s experience across V1 through V3, including features such as eMode, the launch of GHO, and the Safety Module, as the technical and operational foundations that informed V4’s design. He also stressed that the new version isn’t a vacuum project: months of business-development conversations with partners, fintechs, institutions, infrastructure providers and developers shaped the upgrade’s parameters.
Those conversations and the testnet code releases have already been visible to the public and developer community. That context underpins why Aave Labs says it has continued to market and support V3, rather than slowing it in expectation of V4. The company noted that it has actively contributed to integrations on V3 over the past year, and that growth on V3 has not been impeded by the looming V4 launch.
No Hard Pivot
In practical terms, the lab’s approach will be gradual. When V4 approaches mainnet, the rollout will be “slow and responsible,” with capped deposits that scale up over time and an expanding set of collateral types and use cases introduced in stages. This staged plan is intended to preserve the quality and safety standards Aave users expect while enabling new features and capital efficiency improvements.
The timing of Kolten’s clarification arrives amid broader strategic moves from Aave Labs, including the “Aave Will Win” proposal that would redirect revenue from Aave-branded products to the DAO and position V4 as a central axis for future development. That wider strategy has provoked intense governance discussion and media attention, and the lab’s latest messaging appears aimed at calming technical worries even as political and financial debates continue.
Despite the conciliatory tone, the transition has not been free of friction. Some contributors and service providers have voiced reservations about shifting focus toward V4 while V3 remains a cornerstone of current deployments; recent reporting shows at least one major contributor signaling a pullback from governance, citing such disagreements. That kind of tension helps explain why Aave Labs is doubling down on transparency and iterative partner engagement as it tutors the community through the upgrade.
For now, developers and users building on the protocol should read Kolten’s message as an invitation to continue working with V3 without fearing an abrupt sunsetting. The lab’s promise of a cautious, capped rollout for V4 underlines a broader principle: upgrades in DeFi succeed when technical innovation is matched by careful coordination with the people and firms that rely on the code. As Aave edges closer to V4 mainnet, the conversation will likely shift from “when” to “how,” and, for the moment, the answer is clearly “slowly, and with eyes wide open.”
