# Aave Labs Proposes Transient-Storage Guard for V3.8 Pool Operations

By Simon Yoon

Canonical URL: https://www.tokenpost.com/news/technology/37866
Published: 2026-10-22T12:47:11.000Z
Updated: 2026-10-22T12:47:11.000Z
Section: Technology

> The proposal covers active Aave V3 instances on 15 networks, with community feedback, a possible Snapshot vote and audits ahead of an AIP.

Aave Labs proposed Wednesday, Oct. 21, a V3.8 upgrade that would add a reentrancy guard to Pool operations, aiming to protect accounting when transactions return through external contract calls.

The guard would use Ethereum’s transient storage, a space for data that exists only while a transaction is running. A temporary lock there could mark Pool operations so an external callback cannot reenter the Pool and start another operation before the first one finishes. The data is discarded when the transaction ends. Aave Labs’ proposal describes the added gas overhead as low but gives no estimate of its cost or savings.

The proposal addresses a theoretical accounting risk: an outside contract interaction could call back into the Pool during the same transaction, potentially affecting accounting consistency. It does not report an active exploit or a newly discovered vulnerability. The proposed guard is intended to protect Pool operations while those callbacks are in progress.

Aave is a noncustodial liquidity protocol. Suppliers provide funds, and borrowers access liquidity against collateral. The proposed change concerns the Pool operations involved in those transactions.

The rollout would include active Aave V3 instances on Ethereum’s Core and Lido deployments, as well as Plasma, Avalanche, BNB, Monad, Base, Arbitrum, Mantle, X Layer, Polygon, Linea, Optimism, Gnosis, MegaETH and Celo. Instances where all assets are frozen and caps are being set to zero would be excluded.

The governance process begins with community feedback on the Aave Request for Comments (ARFC). If feedback is positive, the proposal calls for an off-chain confirmation vote through Snapshot. Certora and other third parties would audit the upgrade before a formal Aave Improvement Proposal (AIP) is submitted for governance consideration.

Aave V3.8 remains at the proposal stage and has not been approved or deployed. Community feedback is the next step described in the proposal, followed by the conditional Snapshot vote and audits.