Summary
This thread will be used for technical maintenance updates related to Aave V4 to keep V4 maintenance visible, structured, and easy for the DAO to track.
Context
Aave V4 introduces new operational surfaces across Hubs, Spokes, price feeds, permissions, configurator roles, and cross-chain deployment logic. Some updates will be routine maintenance rather than new governance decisions. Keeping those updates in one thread gives the DAO a clear place to review what is changing, why it is needed, and how execution is expected to happen.
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 updates, oracle adapter changes, permission alignment, configurator role updates, Spoke or Hub maintenance, deployment consistency fixes, address registrations, and other changes required to keep V4 components aligned with the approved architecture.
This thread is not intended for new market listings, new collateral onboarding, risk parameter changes that materially affect users, budget approvals, incentive programs, or any change that should go through the normal governance process.
For each maintenance item, Aave Labs will post a standalone update in this thread with the relevant context, affected components, technical specification, execution path, and 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 there are material concerns from the DAO, the item will be moved into the applicable ARFC, Snapshot, or AIP process instead of continuing as a maintenance update.
Disclaimer
Aave Labs is presenting this thread as a service provider to the Aave DAO under the budget approved by the Aave Will Win framework. Aave Labs is contributing this thread as part of its approved scope of work in support of DAO operations.
Copyright
Copyright and related rights waived via CC0.