Aave’s decentralized autonomous organization has signaled broad consensus on advancing the V4 upgrade onto Ethereum’s mainnet. In a near-unanimous Snapshot vote, the DAO backed the deployment path, signaling a move beyond months of internal friction and contributor turnover toward formal on-chain adoption.

The off-chain vote recorded more than 645,000 votes in favor, with fewer than one against and without any abstentions, according to Snapshot data. The overwhelming backing marks a notable shift from earlier governance tensions and sets the stage for an on-chain Aave Improvement Proposal (AIP) vote that would authorize the actual deployment of V4 on Ethereum.

Key takeaways

• Deliberate momentum: The Snapshot result, with near-unanimous support, accelerates Aave V4’s path to Ethereum mainnet, subject to an on-chain AIP vote.
• New architecture, broader use cases: V4 introduces a modular design that separates liquidity from risk, enabling more diverse collateral types and structured credit markets while preserving centralized liquidity depth.
• Governance shakeouts: The vote comes after long-standing contributors exited the DAO, highlighting a turning point in governance dynamics as alignment coalesces around a common deployment plan.
• Next step: The binding AIP vote will determine whether the protocol can activate V4 on Ethereum, moving from proposal to on-chain execution.

Aave V4’s modular design aims to evolve on-chain credit markets

Launched by Aave Labs on March 19, V4 seeks to reimagine how on-chain lending markets are structured. The core idea is to decouple capital from risk management by introducing a two-tier architecture: shared liquidity pools, dubbed “Hubs,” and distinct borrowing environments called “Spokes.” Each Spoke carries tailored risk parameters and exposure limits, enabling the protocol to support a wider array of use cases without sacrificing the depth and efficiency of the unified liquidity pool.

In practical terms, the proposal envisions a framework where new collateral types and structured credit markets can emerge within a unified liquidity system. This modular approach is meant to accommodate assets with varying risk profiles, maturities, or reliance on off-chain data, potentially expanding the range of DeFi products that can be supported by Aave’s core protocol.

Aave Labs underscored that the model preserves the “depth and efficiency of unified liquidity while enabling more precise risk management.” If realized, the change could help the protocol offer more sophisticated credit markets while maintaining capital efficiency for lenders and borrowing flexibility for users.

Governance tensions and the path forward

The push toward V4’s mainnet deployment arrives after a period of notable governance churn. In February, BGD Labs—one of Aave’s longstanding technical contributors—announced its exit after four years, citing an “asymmetric organizational scenario” and what it described as an “adversarial position” toward ongoing work on the existing version. Then in March, The Aave Chan Initiative (ACI), a major governance delegate and service provider, said it would wind down operations following disagreements over governance standards and voting dynamics.

Despite these fractures, the current vote’s outcome implies a broader, cross-community consensus around the direction of the protocol. As Stani Kulechov, founder of Aave, noted, the proposal is expected to advance to an AIP, a binding on-chain vote that would enable the actual deployment and activation of V4 on Ethereum. The exchange between competing viewpoints in recent weeks appears to have given way to a shared sense of where the project must head for the future.

What this means for users, builders, and investors

For users, the V4 upgrade represents a potential expansion of the DeFi toolkit. The modular architecture could unlock new asset classes and risk profiles, enabling more nuanced borrowing strategies and potentially more efficient capital use across on-chain markets. For builders, the shift toward hubs and spokes may offer clearer interfaces and modular upgrade paths, reducing risk integration friction as new collateral types and credit products are introduced.

Investors and liquidity providers may view the move as a test of governance resilience amid contributor turnover. The near-unanimous support in the Snapshot vote signals that a critical mass of the community is confident in the upgrade’s long-term value, even as the DAO navigates the complexities of on-chain governance and contributor dynamics. If the AIP passes, deployment on Ethereum would mark a concrete milestone in Aave’s evolution from a multi-vaceted governance experiment to a more codified, on-chain credit protocol architecture.

Looking ahead, the essential question centers on the timing and outcome of the on-chain AIP vote. While the community appears aligned on the strategic direction, actual deployment hinges on the binding on-chain decision. Market participants should watch not only the vote result but also how the new architecture performs in practice, including risk controls, collateral onboarding timelines, and the integration path for existing liquidity providers.

As the Aave community steers toward the AIP phase, observers will be assessing how governance mechanisms adapt to a more modular system and whether the exits that punctuated earlier months presage a broader stabilization in voting dynamics. The next few weeks will reveal whether V4’s Ethereum mainnet deployment becomes a defining turning point for Aave and a bellwether for modular DeFi architectures across the broader ecosystem.