Aave executes the v3.3 upgrade across all active instances

What happened

Aave governance executed proposal 252 and upgraded all active Aave v3 instances from v3.2 to v3.3.

What changed

The upgrade replaced pool, configurator, and pool-data-provider implementations; introduced reserve-deficit accounting and deficit-elimination hooks for later Umbrella use; and changed liquidation handling to reduce dust and improve position-wide close-factor behavior.

What did not change

Aave v3.3 did not itself activate Umbrella or prove that future deficits would be covered. The official discussion says deficit accounting remains separate from aToken exchange-rate accounting and does not imply safety or approval.

Confirmed

• BGD Labs states that proposal 252 was approved and executed on February 24, 2025.
• The proposal applied to all active Aave v3 instances.
• The upgrade introduced bad-debt logging and burn functionality plus liquidation-engine changes.
• The proposal cites StErMi, Certora, Oxorio, and Sherlock security reviews.

Still open

• Post-upgrade monitoring was still ongoing in the February 24 update.
• The behavior of the later Umbrella integration and any realized deficit coverage was outside this event.
• Audit completion does not establish absence of defects or advisor suitability.

What it means for an advisor

• Update the Aave memo's liquidation and deficit-accounting description to v3.3 and verify integrations relying on deprecated reserve-data getters.
• Do not describe Umbrella coverage as live solely because v3.3 added compatible accounting hooks.
• Review client and approved-position assumptions across every active Aave v3 instance because the implementation upgrade was global.