Summary
This thread will be used for technical maintenance updates across Aave deployments, to keep maintenance activity visible, structured, and easy for the DAO to track. It covers maintenance updates from November 2026 onward and is open to any DAO Service Provider responsible for a maintenance item.
Context
The Aave ecosystem spans multiple products, versions, and networks. Maintenance tasks are periodically required to keep this infrastructure consistent, secure, and aligned with the approved architecture.
Maintenance updates prior to November 2026 are recorded in the previous maintenance thread, which established a clear and transparent format for this type of change. That thread remains the reference for historical updates. From November 2026 onward, maintenance updates will be posted here, so the DAO has a single place to review what is changing, why it is needed, and how execution is happening.
Scope
This thread is intended for updates that are technical, limited in scope, and not expected to create material community disagreement.
Examples include:
- Price feed and oracle adapter updates, for example when a feed is deprecated or optimized by its provider.
- Oracle changes required by the deprecation or migration of an asset.
- Replacement of auxiliary contracts with improved versions that do not change user positions or existing interfaces.
- Permission and access control alignment, including the removal of roles that are no longer required.
- Consistency updates that reduce differences between Aave deployments, and other changes required to keep components aligned with the approved architecture.
Where a change should go through the normal governance process, such as new asset listings, risk parameter changes that materially affect users, budget approvals, or incentive programs, it will follow the applicable ARFC, Snapshot, or AIP route rather than being handled as a maintenance update here.
How updates will be presented
For each maintenance item, the DAO Service Provider responsible for it will post a standalone update in this thread, structured as Simple Summary, Motivation, and Specification. Each update will describe the affected components, the contracts and functions involved, the execution path, and the expected user impact.
Where the update requires an onchain governance proposal, the post will be shared before the AIP is created. Where the update is executed through an authorized operational multisig or Security Council path, the post will explain that execution path and why it applies. If timing or security constraints require execution before public disclosure, the update will be posted as soon as practical after execution.
As a baseline, maintenance updates will remain open for community review before execution or AIP creation when timing allows. If the DAO raises material concerns about an item, it will be moved into the applicable ARFC, Snapshot, or AIP process instead of continuing as a maintenance update.
Disclaimer
Aave Labs is sharing this update as a service provider to the Aave DAO, as part of its approved scope of work in support of DAO operations.