Aave proposes emergency roles that can freeze markets but cannot unfreeze them
Aave governance vote on emergency risk controls
Aave’s decentralized autonomous organization (DAO) is voting on a proposal that would give a group called Risk Stewards limited control over V4 risk parameters on the Ethereum and Avalanche blockchains. The proposal also creates emergency roles that could freeze markets, but the current software cannot use those emergency powers yet.
Key points
- Risk Stewards would receive Hub and Spoke risk‑management and emergency roles with no execution delay.
- Emergency functions can only halt or pause assets; they cannot restart or unfreeze them.
- The Snapshot vote started on Sep 3 2026 at 15:46 UTC and closes on Sep 6 2026 at the same time.
- Even if the vote passes, the changes require execution by the Aave V4 Security Council.
- Risk Steward contracts are undergoing a Certora audit that is close to finalization.
What the proposal adds
The proposal splits V4 configuration into five granular roles: two flag‑control roles, a listing role, an emergency role, and a risk‑management role. Existing domain administrators keep their current reach through the new roles. The emergency role is designed for one‑way safety actions such as deactivating assets or pausing reserves.
Current limitations of emergency powers
According to the steward documentation, the emergency selectors are not exposed in the current release, so the newly assigned emergency roles cannot be exercised until a future software update adds support. This means the system can freeze markets but cannot unfreeze them until later.
Voting timeline
The Snapshot voting page opened on Sep 3 2026 at 15:46 UTC and is scheduled to close on Sep 6 2026 at the same time. A successful vote does not automatically activate the new roles; the Security Council must later execute the payloads.
Audit status
Aave Labs noted in the governance proposal that the Risk Steward contracts are undergoing a Certora audit and that the engagement is nearing finalization.
Community concerns
Forum participants have asked for public rationales, post‑action reports, periodic reviews, and reporting on the frequency and size of steward actions. The current proposal does not require any of these reporting measures.
Next steps after voting
If the Snapshot vote passes, the Security Council will need to execute the payloads to grant the Risk Stewards the no‑delay parameter controls. The emergency powers will be pre‑positioned for a future release but will remain inactive until then.
