Aave Risk Stewards Trim Borrow Rates After Reserve Freeze Tied to Binance Incident

Aave's risk service provider LlamaRisk posted a governance proposal on October 30, 2026, recommending temporary reductions to Slope2 borrow-rate parameters on Aave V3 and Aave V4. Per the proposal on Aave's governance forum, the changes follow "the freeze of Aave V3 and Aave V4 reserves in response to the Binance hot wallet incident on October 29, 2026."

LlamaRisk's October 30 proposal recommends cutting Slope2 for stablecoin reserves, and for WETH on the Aave V4 Ethereum Core Hub, so that the variable borrow rate at full utilization does not exceed 10.00% APR. The base rate, Slope1, and the optimal utilization point are left unchanged under the proposal, meaning borrow rates at or below the optimal point are unaffected. Per the forum post, the adjustments apply only to reserves with more than $10 million supplied, utilization above or within five percentage points of the optimal point, and a borrow curve that would otherwise push rates past the 10% ceiling under current freeze conditions.

Parameter changes preceded the freeze response

The October 30 Slope2 proposal did not arrive in isolation. A day earlier, on October 29, 2026, LlamaRisk had already posted two separate sets of parameter adjustments covering both protocol versions. The Aave V4 proposal, dated October 29, recommended raising the USDC add cap on the Core Hub Main Spoke from 75 million to 85 million, raising the USDC draw cap on the same spoke from 36 million to 60 million, and adjusting Slope1 rates for USDC across the Core and Prime Hubs in opposite directions.

A companion Aave V3 proposal, also dated October 29, recommended raising USDT's optimal usage ratio on Aave V3 Core from 92.00% to 94.00%, alongside supply-cap and Slope1 adjustments spanning Base, Avalanche, Arbitrum, and X Layer deployments. LlamaRisk attributed those October 29 changes to routine review of "user behavior, on-chain liquidity, and position health" rather than to the Binance-linked freeze, which the governance forum post dates to the following day.

CoinsCipher has not independently verified the scope or mechanics of the Binance hot-wallet incident referenced in LlamaRisk's October 30 post; the governance forum entry names the incident but does not describe it in detail, and no separate Binance disclosure has been located on Binance's own channels as of this writing.

What the rate ceiling changes signal

The sequencing matters for anyone tracking DeFi lending markets: the October 29 cap increases were presented as ordinary risk-parameter tuning, while the October 30 Slope2 cuts were explicitly tied to an emergency reserve freeze. That distinction, drawn directly from LlamaRisk's own forum language, separates routine governance maintenance from incident response within a 24-hour window on the same protocol.

Readers tracking Aave exposure should watch whether LlamaRisk or Aave governance publishes a fuller account of the Binance hot-wallet incident itself, since the October 30 post addresses only the downstream rate-parameter consequences for Aave's own markets, not the originating event.