Status as reported November 12, 2026, at 11:22 a.m. UTC+8: Aave V3.8 was live in active Aave V3 markets across 15 chains following Aave DAO approval, according to Deep Tide TechFlow’s original report. Developed by Aave Labs, the upgrade adds core-level protection against reentrancy during external callbacks from pool operations. Frozen legacy markets with limits set to zero were excluded.
Governance and deployment timeline
Aave Labs posted the V3.8 governance-forum proposal on October 21 and submitted it to Snapshot voting on October 27. The community opened the onchain vote for AIP #541 on November 9. The version was deployed by November 12, 22 days after the forum proposal.
The deployment covered Ethereum’s Core and Lido instances, plus active markets on Plasma, Avalanche, BNB Chain, Monad, Base, Arbitrum, Mantle, X Layer, Polygon, Linea, Optimism, Gnosis, MegaETH and Celo. Citing DeFiLlama data as of November 12, TechFlow reported more than $16.4 billion in Aave total value locked, including more than $15.23 billion in active V3 markets. Those figures describe the protocol at the reporting date, not funds individually migrated by the upgrade.

What changed
V3.8 uses EIP-1153 transient storage for its reentrancy lock. As described in the report, TSTORE and TLOAD cost 100 gas per operation, and transient storage clears at the end of a transaction. This avoids maintaining a persistent lock, whose gas cost is affected by the storage-refund limit introduced under EIP-3529.
Aave Labs said the flashLoan and flashLoanSimple entry points check the lock without setting it. That permits a flash-loan callback to combine operations such as liquidation, deposit or repayment. Conversely, an attempt to initiate a flash loan while an ordinary pool-operation callback is in progress is blocked and reverted.
Before the AIP vote, V3.8 underwent Certora formal verification and an independent external security audit, according to the report. The contract code was published in the official Aave V3 repository under a Business Source License. Community developers also cautioned integrations reading pool view functions during callbacks—including account health factors or reserve data—to account for the possibility that the underlying ledger is in an intermediate state.
Source: techflowpost.com (originally published 2026-11-12 11:22 UTC+8)



