Aave DAO votes on limited V4 risk controls and emergency roles

Aave DAO voters are currently deciding on a governance proposal that would delegate limited V4 risk controls to designated Risk Stewards on both Ethereum and Avalanche. The vote, opened on September 3 and closing on September 6, would assign both risk‑management and emergency roles without execution delay.

Proposed role structure

The proposal splits each V4 instance’s configurator controls into five granular categories: two flag‑control roles, a listing role, an emergency role, and a risk‑management role. Existing domain admins would retain their reach through the new roles.

Emergency permissions

Emergency roles would allow Hub calls to deactivate or halt assets and Spokes, and Spoke calls to pause or freeze individual or all reserves. These actions are one‑way only; the same roles cannot reactivate, unhalt, unpause, or unfreeze markets. The current steward software does not expose these emergency selectors, meaning the permissions would remain inert until a future release adds support.

Parameter update limits

Routine updates to interest rates, collateral factors, liquidation settings, and oracle caps would be subject to minimum cooldown periods of 36, 48, or 72 hours and caps on how far parameters can move. These bounds apply equally on Ethereum and Avalanche and do not affect emergency selectors.

Governance and execution

Even if the Snapshot vote passes, the changes would not activate automatically. Aave Labs indicated that the V4 Security Council must still execute the corresponding payloads. The Risk Steward contracts are undergoing a Certora audit, but the code has not been presented as fully audited.

Accountability concerns

Forum participants have called for public rationales, post‑action reports, periodic reviews, and reporting on steward activity. The current proposal does not mandate any of these measures.