Aave V3.8 Officially Launches: Covering 15 Public Chains, $15.2 Billion Liquidity Pool, Introducing Low-Gas-Cost Reentrancy Protection
Aave has launched V3.8 across 15 active V3 markets, following approval by the Aave DAO and development by Aave Labs. According to DeFiLlama, Aave's total value locked exceeds $16.4 billion, with active V3 markets holding over $15.23 billion. The upgrade was deployed via AIP #541, completing a 22-day governance process that began with a forum proposal on October 21 and a Snapshot vote on October 27.
V3.8 covers active instances on Ethereum (Core and Lido), Plasma, Avalanche, BNB Chain, Monad, Base, and Arbitrum, along with Mantle, X Layer, Polygon, Linea, Optimism, Gnosis, MegaETH, and Celo. Legacy markets that were frozen with zero caps were deliberately skipped.
The release introduces kernel-level reentrancy protection for external callback operations on liquidity pools. Traditionally, preventing cross-function reentrancy requires writing a lock flag before state changes, but after EIP-3529 capped SSTORE refunds at 20%, maintaining persistent locks in high-frequency lending pools became gas-intensive. V3.8 instead uses EIP-1153 transient storage, where TSTORE and TLOAD cost only 100 gas per read or write and automatically clear at transaction end, providing reentrancy hardening at minimal cost.
Aave Labs addressed developer concerns that the lock might block liquidation composability within flash loan callbacks. The flashLoan and flashLoanSimple entry points only check the lock status without setting it, creating asymmetric isolation: users can still compose liquidations, deposits, or repayments inside a flash loan callback, but attempts to initiate a flash loan from within a regular pool operation callback are rejected and reverted.
Security verification included Certora formal verification and independent external audits before the AIP vote. The new contract code is published in the official Aave V3 repository under the Business Source License. Developers also noted that downstream integrators reading view functions such as account health factors or reserve data during callbacks should account for intermediate ledger states and ensure peripheral risk controls remain compatible.
marsbit33m ago