KOSUNI CRYPTO
Korea's Crypto Pulse, in English
$BTC $ETH $XRP $SOL $DOGE
DeFi
Neutral

Aave V4 Risk Management Role Division Under Discussion, Freeze Release via Governance

Published September 25, 2026 5:48 AM · 8 views $AAVE $AVAX $ETH
Aave V4 Risk Management Role Division Under Discussion, Freeze Release via Governance

Aave (AAVE) is discussing a proposal to segment the risk adjustment authority for its V4 Ethereum (ETH) and Avalanche (AVAX) instances. The plan allows halting or freezing markets in emergencies but reserves the power to reverse such actions for governance. Aave Labs announced the 'Activate Aave Risk Stewards on Aave V4' proposal on its governance forum at 8 a.m. KST on August 21, suggesting activating risk stewards for both Ethereum and Avalanche V4 instances. The proposal entered the snapshot phase on September 3, with Diggrove Atlas showing three active proposals in the Aave DAO as of September 7.

The core idea is avoiding centralized management authority. The proposal divides each instance's configuration administrator role into five specific roles: △All activity block △New activity block △Listing △Emergency response △Risk management. Risk management handles adjustments to certain risk variables within defined limits and cooldown periods, such as hub optimal utilization rates, base borrowing rates, interest rate increases, additional caps, and withdrawal limits. Emergency roles only manage functions like deactivation, suspension, or freezing for safer states but will not be active in this release.

Aave Labs stated in the proposal that 'this release does not call these selectors,' meaning emergency powers will remain inactive until future releases. Risk management targets include hub-based optimal utilization rates, base borrowing rates, interest rate increases, additional caps, and withdrawal limits with cooldowns of 36 or 72 hours per item—48 hours for the penalty discount rate. Adjustments are limited by absolute or relative values depending on the item.

This proposal aligns with Aave V4's structure, which separates liquidity aggregation (hub) from user loan logic (spoke). Aave Labs previously explained in its March V4 activation document that the hub manages shared liquidity and emergency halts while spokes handle lending environments and reserve settings. This design reflects a trend where large DeFi protocols struggle to manage risks across multiple markets centrally.

Typically, DeFi lending markets adjust collateral ratios, borrowing limits, interest rate curves, and oracle benchmarks together. Without decentralized authority, response times slow down. Aave Governance Framework v2 also supports this direction, noting that freeze stewards can immediately halt new supply and borrowing but require governance to lift freezes.

As delegation expands, oversight becomes a key issue. MconnectDAO asked in the forum whether major risk steward actions should include public justification, usage data, expected impact, alternative reviews, and post-implementation reports—a call for speed alongside accountability. Abel189 commented that 'a limited access approach seems reasonable' but stressed that DAOs need regular reporting on the scale and frequency of variable changes to assess delegated authority use.

Aave Labs' September 1 development update noted V4 deposits exceeded $800 million (around 1.8 trillion KRW) in August, with active loans hitting an all-time high. The same update reported three adjustments to supply and borrowing caps on both Ethereum and Avalanche since the V4 risk stewards were activated.

Investors should note that Aave V4's metrics require careful interpretation: deposits, total value locked (TVL), and active loans are different indicators of protocol usage with varying calculation methods. For domestic investors, this discussion holds significance beyond governance procedures, as large DeFi protocols like Aave directly impact user positions through collateral values and borrowing limits. However, the proposal addresses risk parameters and authority allocation rather than investment returns. As of September 7, it remains unclear whether the Aave DAO has approved or executed the proposal; next steps involve snapshot verification followed by payload execution via V4 Security Council.

Korean Source

This article is an English localization of a Korean-language crypto news report. Original headline: 에이브 V4 권한 세분화 논의, 동결 해제는 거버넌스로