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

Published 2026-10-22 · Crypto.world Team · Crypto.world

> Aave Labs proposed Aave V3.8 on Oct. 21, 2026, adding a transient-storage reentrancy guard to Pool operations. The proposal targets active Aave V3 deployments across 15 networks and calls for audits before an on-chain upgrade proposal.

[Aave](https://governance.aave.com/t/arfc-aave-v3-8/25891) Labs proposed adding a transient-storage reentrancy guard to Aave V3 on Oct. 21, describing the planned V3.8 release as a limited security update rather than a broad protocol redesign. The proposal covers active Aave V3 instances across 15 networks, but it has not yet reached an on-chain vote: community feedback, a Snapshot vote and security audits come first.

## Aave V3.8 targets repeated Pool interactions

The proposed guard is intended to protect Pool accounting when an external callback returns control to the Pool during a transaction. A transaction can interact with the Pool more than once; the proposal says the guard is designed to keep accounting consistent through that execution flow and reduce exposure to theoretical reentrancy exploits.

“Aave V3.8 introduces a guard based on transient storage (EIP-1153) that protects Pool accounting consistency, including when a single transaction’s execution flow interacts with the Pool more than once,” AaveLabs writes in the proposal. The change uses transient storage for the guard and is presented as carrying little overhead, addressing the gas-cost concern the proposal says historically constrained this type of protection.

## Fifteen networks are named in the rollout

The proposed upgrade targets Ethereum’s Core and Lido instances, plus deployments on Plasma, Avalanche, BNB, Monad, Base, Arbitrum, Mantle, X Layer, [Polygon](https://crypto.world/companies/polygon-labs), Linea, [Optimism](https://crypto.world/companies/op-labs), Gnosis, MegaETH and Celo. Aave Labs limits the plan to active instances. Deployments where all assets are frozen and caps are being set to zero are excluded.

The network list describes the intended scope, not completed upgrades. The post does not give a deployment schedule or say that V3.8 is live on any of the named networks. Aave governance would need to advance the proposal through its stated process before the upgrade could proceed.

## Audits precede an on-chain proposal

Aave Labs says Certora and third parties will audit V3.8 before an Aave Improvement Proposal, or AIP, is submitted. The immediate step is community feedback during the ARFC stage. If that response is positive, the proposal will move to an off-chain Snapshot vote; after the audits, an AIP would seek approval to upgrade the instances in scope.

The proposal also sets out a licensing condition: V3.8 will be published as a separate Licensed Work under a Business Source License. Aave governance will set its change date and record it in a text record at v38.aavelicense.eth; until then, the code remains under that license. Aave Labs says transferring the V3.8 intellectual property to the Aave Foundation would require a separate governance proposal.

## The proposal is a defense-in-depth change

Aave Labs frames the update as a measured security improvement, not a response to a disclosed exploit. The forum post says further security reviews are being planned and leaves open the possibility of additional defense-in-depth improvements in later upgrades. For now, V3.8 remains at the ARFC feedback stage, with audits and governance approvals still ahead.

## Sources

1. Original source [Aave Governance Forum](https://governance.aave.com/t/arfc-aave-v3-8/25891) governance.aave.com

## Companies in this story

- [Aave Labs](https://crypto.world/companies/aave-labs)

## Related stories

- [Aave Risk Stewards Propose Five Borrow-Cap Increases After Debt Rebounds](https://crypto.world/news/aave-risk-stewards-propose-five-borrow-cap-increases)
- [Aave community proposes study of temporary borrowing controls](https://crypto.world/news/aave-community-proposes-temporary-borrowing-controls-study)
- [LlamaRisk proposes Aave V3 borrowing rate limits](https://crypto.world/news/aave-llamarisk-proposes-dynamic-borrow-caps)
- [Aave proposal would narrow V3 Core to established collateral](https://crypto.world/news/aave-proposal-narrow-v3-core-collateral)
- [Shaw Rebuilds daos.fun’s Solana Program Byte for Byte, Reports a Critical Flaw](https://crypto.world/news/shaw-daos-fun-solana-program-critical-flaw)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/aave-v3-8-transient-storage-security-proposal
