How Aave's GHO Liquidity Committee Went Off-Script

Even as the bear market pushed many DeFi projects into decline, Aave's governance activity continued largely unabated — though not always in an orderly fashion.

Concerns about cascading liquidations linked to the Curve Finance pool exploit had already put some community members on edge. Separately, an Immunefi bug bounty program surfaced several vulnerabilities — including inconsistent borrow-rate validation and a price-manipulation issue — which fortunately were caught by white hat researchers rather than exploited.

Layered on top of this, Aave was in the middle of rolling out multi-chain governance following its v3 upgrade, adding to an already active period for the protocol's community decision-making. Aave had also launched its own stablecoin, GHO, in the summer of 2023, which struggled to hold its peg, prompting governance-approved rescue efforts.

The GHO Liquidity Committee

GHO's peg instability was compounded by the token's lack of a redemption mechanism allowing holders to swap it directly for one dollar. In response, Aave governance formed the GHO Liquidity Committee (GLC) to manage the peg.

One committee member, described as a liquidity expert, reportedly complained that the committee lacked sufficient additional expertise, then was subsequently voted in as "temporary and benevolent leader" of the committee.

Rather than strictly following the governance-approved process, the committee deviated from its mandate. The plan, approved through a governance proposal, called for minting and staking sdCRV to a Gnosis Safe requiring 4-of-5 signers to authorize transfers. Instead, the committee sent cvxCRV — a different token than what governance had approved — across two transactions:

• Transfer 1 (1.05M cvxCRV)
• Transfer 2 (1.05M cvxCRV)

A resignation and its aftermath

Just over a week after these transfers, the committee's leader resigned, then published a critical post on X and a blog entry — including remarks critical of sdCRV, the very token the committee had been directed to transfer instead of cvxCRV.

In his writing, Token Brice criticized both the GLC's liquidity decisions and the broader Aave governance process, alleging that key discussions were happening privately rather than in view of the community — a complaint made notable by the fact that the cvxCRV transfer decision itself was made outside the approved process, under his leadership. Because moving funds from the safe required four of five signers to agree, the deviation from the approved plan would have needed cooperation from others on the committee, not unilateral action.

Fallout for Aave

Separately, risk management firm Gauntlet ended its relationship with Aave around this period. Gauntlet co-founder John Morrow stated that his team had struggled with "inconsistent guidelines and unwritten objectives" set by Aave's largest stakeholders.

The episode raises questions about whether a governance committee deviating from an explicitly approved transfer plan could have been avoided, and about the broader tension in DeFi between decentralization's goal of distributing decision-making power and the reality of concentrated influence among a small number of active participants. Aave is not the only protocol to have encountered friction of this kind as the space matures; some observers have pointed to no-governance models, such as Liquity's, as an alternative worth considering.

Overall, the GHO-GLC episode illustrates the practical difficulties of enforcing governance decisions even when a clear, voted-upon process exists, and underscores the gap that can emerge between what a DAO approves and what its appointed committees actually execute.