Aave DAO Backs V4 Mainnet Plan in Near-Unanimous Vote

Aave V4 just cleared its biggest political hurdle. On Monday, the Aave DAO voted in near-unanimous fashion to back the V4 protocol's deployment on Ethereum mainnet — 645,000 votes in favor, fewer than one against, zero abstentions — numbers that signal a community ready to move forward after one of its rougher stretches of internal conflict.

What Is Aave V4 and What Changes?

Aave V4 is a ground-up redesign of the lending protocol's architecture, proposed by Aave Labs on March 19. The core shift: a modular Hub and Spoke model that separates shared liquidity from the distinct risk environments where that liquidity gets deployed. In plain terms, capital sits in shared pools (the Hubs), and individual borrowing markets (the Spokes) pull from those pools while maintaining their own risk parameters and exposure limits.

That distinction matters more than it sounds. Today's monolithic lending pools mean one bad asset can bleed into an entire market. The Hub and Spoke design is meant to contain that contagion — letting the protocol support riskier or more exotic collateral types without threatening the whole liquidity pool. Aave Labs said the structure preserves liquidity depth while enabling "more precise risk management" across different asset classes.

The design also targets a broader range of financial use cases — assets with different maturities, offchain dependencies, or non-standard risk profiles. Structured credit markets, new collateral types, tokenized real-world assets: the V4 framework is built to accommodate them without bolting on workarounds to an architecture that was never designed for that complexity.

The design preserves the depth and efficiency of unified liquidity while allowing for more precise risk management.

How Did the Aave DAO Governance Vote Play Out?

The Aave DAO governance vote on Snapshot came out about as one-sided as governance votes get. More than 645,000 votes landed in the "yes" column. Fewer than one vote registered against. Not a single abstention. For context: this is a DAO that spent the prior two months publicly fracturing — watching core contributors walk out the door and governance delegates trade accusations in public forums.

The Snapshot vote is offchain, so it's not binding on its own. What it does is clear the political path toward a formal Aave Improvement Proposal — the onchain AIP vote that would actually authorize V4's deployment and activation on Ethereum. Founder Stani Kulechov confirmed the proposal is expected to advance to that stage. Once it does, the community's near-unanimous backing becomes a formal protocol upgrade.

That sequence — Snapshot temperature check, then binding AIP — is standard Aave governance procedure. The unusual part here isn't the process. It's how clean the result was, given the turbulence leading up to it.

Why the Governance Context Actually Matters Here

Call it a reset, or call it a redirect. Either way, the V4 vote landing this cleanly is notable precisely because of what came before it. On February 20, BGD Labs — a technical contributor that had worked alongside Aave for four years — announced it was ending its involvement with the protocol. The stated reason: an "asymmetric organizational scenario" and what BGD described as an adversarial position toward its work on the existing codebase. That's contributor-speak for 'we're not being treated fairly, and we're done.'

Then on March 3, the Aave Chan Initiative followed. ACI founder Marc Zeller said the organization would wind down operations after a clash over a proposed funding package. His complaint was about governance standards and voting dynamics — the mechanics of how decisions get made and who has real influence over them.

Two major contributors out the door in two weeks. That's the kind of thing that stalls protocols, sometimes for years. The fact that V4 sailed through with this kind of support just weeks later suggests either the community made peace fast, or the departures removed the friction that was holding the vote back. Probably both.

For anyone watching AAVE from the outside, the governance drama was always the bigger risk than the technical roadmap. V4's architecture was never the controversy — the question was whether the humans running the DAO could get aligned enough to ship it.

What Comes Next for Aave V4?

The next step is the binding AIP vote onchain. If that clears — and given the Snapshot result, there's no real reason to expect it won't — Aave moves into the actual deployment and activation phase of V4 on Ethereum mainnet. No timeline has been announced publicly beyond Kulechov's confirmation that the AIP process is the immediate next step.

What V4 means in practice for users depends on how quickly new markets and collateral types come online under the new architecture. The Hub and Spoke model gives the protocol more surface area to work with — but more surface area also means more attack vectors, more auditing, more risk surface to manage. Aave Labs will need to make those tradeoffs visible to the community as deployment progresses.

The governance wounds from BGD Labs and ACI's departures haven't magically healed. Those contributors took institutional knowledge with them. But for now, the DAO has spoken — loudly, and in one direction.