Aave Labs confirms execution of V3 low-adoption reserve deprecation

What happened

Aave Labs' September update confirms execution of low-adoption asset deprecation on Aave V3 through AIP 521.

What changed

The official execution report establishes a reserve wind-down affecting Aave V3's supported exposure perimeter.

What did not change

The separate oracle-deprecation AIP is described as still in preparation. The update does not establish exact wind-down parameters or consequences for any particular client position.

Confirmed

• Aave Labs identifies AIP 521 as the executed V3 low-adoption deprecation action.
• The stated purpose is winding down reserves with limited adoption.
• The separate V2/V3 oracle-deprecation action is not reported as executed.
• The update was published October 1 and describes September activity.

Still open

• Exact execution date, transactions, affected reserves, and payload parameters.
• Whether any approved research route uses a deprecated reserve.
• Required migration or repayment steps for affected positions.

What it means for an advisor

• Review the Aave V3 memo's supported-reserve inventory against AIP 521 before reaffirming affected routes.
• Resolve the payload and exit mechanics before recording any specific user action.