Aave Labs’ 21 October V3.8 proposal would add a reentrancy guard to Pool operations during external callbacks. The draft presents it as preventive hardening against theoretical exploits, without reporting a current loss or emergency deployment.

What changes inside a transaction

The design uses EIP-1153 transient storage. Aave Labs says this would help preserve Pool accounting when execution returns to the Pool within one transaction, with limited extra gas cost.

The Ethereum specification describes storage that lasts only until a transaction ends. Its TLOAD and TSTORE instructions let a contract share temporary state between calls, making them useful for reentrancy locks. The specification also warns that incorrect clearing can block later interactions within that transaction; the instruction set alone does not establish that an implementation is safe.

Approval and deployment are still ahead

The proposed rollout covers active V3 instances across Ethereum and other supported networks. Pools being wound down, with every asset frozen and caps moving to zero, would be excluded.

The stated sequence is community feedback, a Snapshot decision if feedback is positive, audits by Certora and other reviewers, and an implementation proposal. The draft supplies no completed audit or executed upgrade. V3.8 would initially use a Business Source License, with governance setting its change date.

NetNapz assessment

The practical milestone is a reviewed implementation and a verifiable governance execution. A proposal can explain a security objective, but users and integrators still need the final code, audit findings and deployment addresses to establish which pools have changed.

This is a maintenance proposal for V3. It should be assessed separately from Aave’s USAT and permissioned GHO proposals, which concern a different product configuration. No token-price effect is established by the security announcement.

Verification limits

NetNapz checked the governance post and EIP-1153 on 22 October. Approval, audit completion and live deployment remain unverified. This pass did not inspect deployed bytecode.