Aave's Risk Stewards, led by LlamaRisk, have proposed parameter adjustments across multiple instances of the protocol based on current liquidity conditions and borrower health metrics. The recommendations reflect diverging patterns: X Layer requires expanded capacity to accommodate demand, while Avalanche faces migration pressures that warrant tighter guardrails. These moves illustrate how Aave governance continuously calibrates risk parameters to reflect changing market dynamics and user behavior on different blockchain deployments.
On Aave V3's X Layer deployment, USDe (Aave's native stablecoin) has reached 72.5% of its 35 million borrow cap, signaling constrained availability despite adequate supplied liquidity. LlamaRisk's analysis reveals that top borrowers maintain relatively healthy health factors between 1.03 and 1.10, with the largest borrower representing roughly one-third of total debt. Eighteen of the twenty largest borrowers pledge PT-USDG-25FEB2027 perpetual tokens as collateral, creating a concentration risk tied to a specific yield instrument's price performance. The recommendation to double the borrow cap to 70 million would reduce utilization to approximately 36%, creating breathing room for legitimate demand while maintaining prudent risk exposure given the collateral composition.
Conversely, WAVAX on Aave V3 Avalanche presents an oversubscription problem. The asset currently exceeds its 14 million cap utilization, sitting at 115.9% as users migrate positions to the newer Aave V4 protocol on the same chain. Rather than increase capacity, LlamaRisk recommends reducing the supply cap to 12 million, which would keep new deposits blocked until existing positions wind down. This measured approach prevents fresh WAVAX exposure from accumulating on a legacy instance while the ecosystem consolidates around newer infrastructure. The asymmetric treatment—expansive for X Layer, restrictive for Avalanche—demonstrates risk management's context-dependent nature across fragmented liquidity pools.
These parameter changes require governance approval and underscore how Aave's multi-chain architecture demands localized risk assessment. As the protocol continues fragmenting across competing L1s and L2s, the coordination between Risk Stewards and governance on capacity management will remain critical to preventing either artificial bottlenecks or dangerous accumulation of tail risks.