# Aave proposes the v3.4 upgrade across all instances

> If executed, the proposal would replace Pool, PoolConfigurator, PoolDataProvider, AToken, and VariableDebtToken implementations, standardize Ethereum Core GHO accounting, add configurable Position Manager permissions, and simplify flash-loan fees.

- URL: https://riadefi.com/on-chain/2025-06-28-aave-v3-all-instances-v3-4-upgrade/
- Type: Upgrade or migration
- Stage: Proposed
- Evidence: confirmed
- Materiality: material
- Event date: 2025-06-28
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2025-07-04
- Advisor-relevant: no
- Affects: Aave v3 (protocol)

## What happened

Aave governance created proposal 334 to upgrade all v3 instances from v3.3 to the reduced v3.4 release.

## What changed

If executed, the proposal would replace Pool, PoolConfigurator, PoolDataProvider, AToken, and VariableDebtToken implementations, standardize Ethereum Core GHO accounting, add configurable Position Manager permissions, and simplify flash-loan fees.

## What did not change

The proposal had not completed voting or execution by June 30. It states that the GHO migration is intended to be non-invasive for users, but that intent does not establish post-upgrade behavior.

## Confirmed

- The payload covers all Aave v3 instances through multiple network payloads.
- The existing native stkAAVE discount on variable-debt GHO would be removed.
- The proposal includes a pre-execution process intended to settle outstanding GHO discounts shortly before execution.
- Four independent audit reports and extensive testing are identified in the proposal.

## Still open

- The vote outcome and execution after June 30.
- The exact GHO balances and facilitator transfers at execution time.
- Post-upgrade verification of every instance and Position Manager configuration.
- Whether any user accounting or integration issue appears after deployment.

## What it means for an advisor

- Open a review of Aave v3 implementation, GHO accounting, delegation, and flash-loan assumptions before treating v3.4 as operative.
- Verify every deployed implementation and Ethereum Core GHO transition after execution; audits do not establish suitability or successful migration.

## Sources

1. [Upgrade Aave instances to v3.4](https://vote.onaave.com/proposal/?proposalId=334) · Aave Governance · 2025-06-28


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.