Eth MeridianETHEREUM / A RESEARCH INDEX
Menu

Aave V3.8 goes live across 15 markets with a new reentrancy guard

As reported on November 12, 2026, Aave V3.8 had gone live across 15 active Aave V3 markets following Aave DAO approval. Developed by Aave Labs, the release adds a reentrancy guard at the pool-contract level for external callbacks. This is an Aave application upgrade, not an activation of an Ethereum protocol upgrade.

Aave Labs posted its V3.8 governance-forum proposal on October 21 and submitted it to Snapshot on October 27. The community opened the on-chain vote for AIP #541 on November 9. The release reached deployment 22 days after the forum proposal.

Aave V3.8 goes live across 15 markets with a new reentrancy guard (1)

The rollout covers active instances on Ethereum—including its Core and Lido markets—Plasma, Avalanche, BNB Chain, Monad, Base, Arbitrum, Mantle, X Layer, Polygon, Linea, Optimism, Gnosis, MegaETH and Celo. Frozen legacy markets with limits set to zero were skipped. According to DeFiLlama figures cited in the report, Aave’s total value locked exceeded $16.4 billion on November 12, with more than $15.23 billion in active V3 markets.

Aave V3.8 goes live across 15 markets with a new reentrancy guard (2)

How the guard works

V3.8 uses transient storage specified by EIP-1153 for its lock. Unlike a persistent storage lock, transient storage clears at the end of a transaction; the reported cost of each TSTORE or TLOAD operation is 100 gas. The design addresses the cost of maintaining persistent locks after EIP-3529 reduced the refund limit for clearing storage to 20%.

Aave V3.8 goes live across 15 markets with a new reentrancy guard (3)

The lock is deliberately asymmetric. Aave Labs said flashLoan and flashLoanSimple check the lock without setting it, so a flash-loan callback can still combine actions such as liquidation, deposit or repayment. A flash loan attempted from within a callback to an ordinary pool operation, however, is blocked and reverted.

Before the AIP vote, V3.8 underwent Certora formal verification and an audit by an independent external security team. The contracts were published in the official Aave V3 repository under the Business Source License. Community developers also cautioned integrators that pool view functions, including account health-factor and reserve-data reads, may expose intermediate accounting states during an external callback; downstream risk checks need to account for that boundary.