Aave founder and CEO Stani Kulechov has responded to recent governance tensions within the Aave ecosystem, outlining a strategic plan to address operational control concerns and accelerate long-term growth. The controversy followed a DAO vote on whether the community should assume full control over the protocol’s brand and front-end assets. The proposal was decisively rejected—with 55% voting against, 41% abstaining, and just 3.5% in favor—highlighting persistent questions around value capture and alignment between Aave Labs and token holders.
In a post on Friday, Kulechov framed the present moment as a crossroads for Aave, emphasizing that the protocol’s growth cannot be limited to its current crypto-native lending products. He sees enormous potential in expanding into real-world assets (RWAs) and institutional markets, projecting that Aave could ultimately support a $500 trillion asset base and onboard tens of millions of users through the Aave App.
Kulechov said:
A core aspect of this strategy is the upcoming Aave V4, a modular architecture designed to integrate new lending models and asset classes safely. The design allows innovation without compromising protocol integrity, enabling both crypto-native and RWA-backed use cases while creating a developer-friendly environment to encourage innovation.
Addressing operational concerns, Kulechov stressed that mainstream consumer-grade products needed to onboard millions of users should be developed by independent, highly autonomous teams on top of the permissionless Aave Protocol rather than funded or controlled directly by the DAO. This approach ensures rapid execution while allowing the protocol to benefit from increased usage and revenue.
Kulechov said:
Kulechov also pledged to share revenue generated outside the protocol with token holders and confirmed that upcoming proposals will include clear guardrails for branding and revenue alignment. In his concluding notes, Kulechov reinforced his belief in Aave’s potential while also appealing for collaboration to drive the protocol and its native token’s success.


