Aave proposes emergency tools that can freeze crypto lending markets but not unfreeze them

Aave DAO is voting on a proposal to delegate limited V4 risk controls on Ethereum and Avalanche to Risk Stewards. The proposal introduces emergency roles that can execute one-way safety actions, such as freezing markets, but cannot unfreeze them. Although these roles would be granted immediately, the current software release cannot use them, pre-positioning the powers for future updates. Additionally, the contracts are still undergoing a Certora audit, and the proposal lacks requested accountability requirements like post-action reports.

Aave V4 Risk Steward proposal

• ▪The Snapshot vote for the Aave V4 Risk Steward proposal opened on September 3, 2026, at 3:46 p.m. UTC and was scheduled to close on September 6, 2026, at 3:46 p.m. UTC.
• ▪Aave DAO voters are deciding on a proposal to delegate limited V4 risk controls on Ethereum and Avalanche to Risk Stewards, which are tools that allow approved operators to make constrained changes without a full governance vote.

Emergency role limitations

• ▪The current Aave Risk Steward software release cannot invoke the proposed emergency roles because it does not call any emergency selectors or expose those methods in its documentation.
• ▪The proposed emergency roles for Aave V4 Risk Stewards are limited to one-way safety actions, allowing operators to deactivate or halt assets and Spokes, or pause and freeze reserves.
• ▪The emergency roles granted to Aave V4 Risk Stewards cannot reactivate, unhalt, unpause, or unfreeze the affected markets, as those two-way state changes require separate flag-control roles.

Governance approval execution requirements

• ▪The proposed permission redesign splits each Aave V4 instance's Hub and Spoke configurator controls into five granular categories, leaving selectors outside these categories with residual domain-admin roles.
• ▪A successful Snapshot vote on the Aave V4 Risk Steward proposal does not activate the system by itself, as the corresponding payloads must still be executed through the V4 Security Council.

Parameter control bounds

• ▪The parameter control bounds under the Aave V4 Risk Steward proposal cover interest-rate settings, collateral factors, liquidation settings, and oracle caps on both Ethereum and Avalanche.
• ▪Routine parameter updates under the Aave V4 Risk Steward proposal require minimum cooldowns of 36, 48, or 72 hours and cap how far each update may move the parameter.

Audit status accountability concerns

• ▪Aave forum participants requested accountability measures including public rationales, post-action reports, and periodic reviews, none of which are required in the current Aave V4 Risk Steward proposal.
• ▪The Aave Risk Steward contracts were not presented as fully audited in the governance proposal, as they were still undergoing a Certora audit that was nearing finalization.

Debatable claims

• ▪Aave should postpone the Risk Steward vote until its audit is fully completed
• ▪Aave should require public reporting for Risk Steward actions
• ▪Aave should delegate risk controls to Risk Stewards

1 source