Aave proposes the v3.4 upgrade across all instances

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.