Aave DAO voters are deciding whether to hand Risk Stewards bounded control of V4 risk parameters on Ethereum and Avalanche, plus zero-delay emergency roles the current steward software cannot yet use. Approval alone would not activate the system — the Security Council would still need to execute the payloads — and the emergency powers can only freeze markets, never unfreeze them.
A Snapshot vote that opened Sept. 3 at 3:46 p.m. UTC and closes today at the same time asks Aave DAO voters to delegate bounded V4 risk-parameter control on Ethereum and Avalanche to Risk Stewards, alongside no-delay emergency roles the current steward software cannot yet use.
Approval would not activate the system on its own. Aave Labs said the corresponding payloads would still need to be executed through the V4 Security Council, and the Risk Steward contracts are undergoing a Certora audit that is nearing finalization, according to the governance proposal.
Emergency powers only freeze, never unfreeze
Each Risk Steward would receive Hub and Spoke risk-management roles plus Hub and Spoke emergency roles, and all four roles would carry no execution delay once granted. But the release under consideration calls none of the emergency selectors, and the current steward documentation does not expose those methods, so the emergency permissions would stay inert until a future release adds support.
The emergency category is limited to one-way safety actions. Hub calls can deactivate or halt assets and Spokes, while Spoke calls can pause or freeze individual reserves or all reserves — but none of those calls can reactivate, unhalt, unpause or unfreeze the affected market. The separate flag-control roles, which can move states in both directions, would not go to the Risk Stewards.
Routine changes face cooldowns of 36 to 72 hours
The wider redesign splits each V4 instance's configurator controls into five categories: two flag-control roles, a listing role, an emergency role and a risk-management role, with existing domain admins keeping their current reach under the new structure. Routine parameter updates carry minimum cooldowns of 36, 48 or 72 hours depending on the parameter, with caps on how far each update can move it, applying equally on Ethereum and Avalanche to interest-rate settings, collateral factors, liquidation settings and oracle caps. Those cooldowns do not constrain the emergency selectors.
No requirement to publish steward actions
That split creates an accountability question, since the zero-delay roles would exist before the steward could use them. Forum participants asked for public rationales, post-action reports, periodic reviews and reporting on the frequency and size of steward actions, but none of those measures appears in the current proposal.
If the Snapshot vote passes and the Security Council executes the payloads, the immediate effect would be no-delay access to bounded parameter controls, while the one-way emergency powers stay pre-positioned but unusable until a later steward release.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
