Aave Risk Stewards Restore Borrow Rates After Binance Hack Freeze

Aave's risk service provider LlamaRisk restored Slope2 interest-rate parameters across Aave V3 and Aave V4 reserves to their pre-incident levels on October 31, 2026, reversing emergency rate cuts it had put in place a day earlier, according to a governance forum post published on Aave's governance forum.

Why Aave Cut Rates in the First Place

The reversal closes a two-day episode that began after what the governance post describes as "the Binance hot wallet incident of October 29, 2026." LlamaRisk had responded to that incident with a package of defensive measures published October 30, 2026, starting with a temporary reduction of Slope2 parameters on Aave V3 and Aave V4 reserves. Slope2 is the steeper portion of Aave's interest-rate curve that applies once a reserve's utilization passes its optimal point, and lowering it reduces the cost of borrowing at high utilization levels, which in turn discourages rapid liquidity withdrawal during stress.

The same day, LlamaRisk also posted a separate measure cutting borrow and draw caps on Aave V3 and Aave V4, a complementary move that limits how much additional debt can be issued against affected reserves while conditions remain uncertain. Together, the two October 30 actions functioned as a liquidity circuit breaker: slow new borrowing, soften the rate penalty for utilization spikes, and buy time to assess exposure tied to the Binance incident.

What Changed in the October 31 Reversal

The October 31 post states that the affected reserves "are no longer frozen" and that the base rate, Slope1, and optimal utilization point were left unchanged throughout, meaning borrowing costs at or below the optimal utilization point were unaffected by either the cut or the restoration. The specific reversions disclosed in the post include raising Slope2 for USDC from 5.50% back to 10.00%, for USDT from 5.50% back to 10.00%, and for DAI from 15.00% back to 35.00%, returning each parameter to its pre-incident setting.

LlamaRisk's post does not elaborate on what specifically about the Binance hot wallet incident posed risk to Aave's reserves, nor does it specify when or how the determination was made that reserves were "no longer frozen." Those mechanics are not addressed in the governance thread as published.

The sequence illustrates how Aave's risk stewards use parameter adjustments, rather than pauses or freezes of the protocol itself, to manage spillover risk from exchange-level incidents. For holders using DeFi lending markets, the episode is a reminder that interest-rate curves on platforms like Aave can move in response to external shocks unrelated to the protocol's own code, and that such adjustments are typically reversed once risk providers judge the underlying exposure has passed. Whether LlamaRisk or Aave publishes further detail on the Binance-related exposure that triggered the October 30 measures remains to be seen.