- Aave cut borrow caps across several reserves on October 30, 2026 during its response to the Binance security incident, and those caps stayed reduced even after the underlying markets were unfrozen later that same day
- By November 1, 2026, utilization on five of those reserves had climbed back to between 98.3% and 100% of the lowered caps, prompting Aave’s risk manager to recommend raising them again
- The pattern shows DeFi risk parameters moving in both directions in quick succession: tightened defensively during a crisis, then loosened again once normal demand reasserts itself against an artificially low ceiling
When Aave responded to the Binance security incident on October 29 and 30, 2026, its most visible action was freezing markets outright, blocking new supply and new borrowing on more than 175 reserves across 16 networks. Less visible, but just as consequential, was a second layer of defense: Aave also lowered borrow caps on several reserves on October 30, a more targeted restriction than a full freeze that limits how much of a given asset can be borrowed in total, even after the freeze itself is lifted.
What makes this sequence worth examining is how quickly the lowered caps became a practical constraint on ordinary activity, separate from the crisis that caused them. By November 1, 2026, just two days after the initial defensive reduction, utilization against those reduced caps had already climbed to between 98.3% and 100% across five separate reserves spanning four different Aave V3 deployments, essentially maxing out the available room to borrow against assets like WETH, EURC and USDT0.
Aave’s risk manager, LlamaRisk, responded by recommending increases to all five caps on November 1, 2026, restoring additional borrowing capacity while still leaving the caps somewhat below where they presumably stood before the crisis began. The specific numbers show the adjustments were incremental rather than a full reversal: WETH’s borrow cap on Aave V3 Core moved from 1,790,000 to 1,810,000, for instance, a meaningful increase but not necessarily a full return to pre-incident levels.
This pattern illustrates something important about how risk management works in a protocol like Aave, which relies on a dedicated risk-steward process specifically designed to make fast, incremental adjustments without needing a full governance vote each time. A defensive tightening made in the heat of a crisis is not meant to be permanent; it is meant to buy time for the situation to stabilize, after which the same quick-adjustment tools that imposed the restriction can be used to relax it again as real usage data shows the lowered limit is now constraining ordinary activity rather than protecting against an active threat.
The speed of this round trip, from defensive cut to utilization-driven increase in a matter of days, offers a useful window into how actively major DeFi protocols now manage their own risk parameters in response to both crises and the ordinary ebb and flow of user demand. The cap increase recommendation is posted on Aave’s own governance forum.
Disclaimer: Cryip's content is strictly for educational and informational purposes and does not constitute financial, legal, or investment advice. Cryptocurrency involves significant risk, and readers assume full responsibility for their own financial decisions. Asset references are never endorsements.
To make complex crypto topics accessible to readers at all experience levels, our team uses AI tools strictly to refine language, correct grammar, and simplify terminology. AI is never used to draft facts, source information, or form conclusions. Every article is fact-checked and approved by a human editor before publication. Read our full AI Use & Content Policy.
