Horizon Technical Maintenance Updates

Summary This thread will be used for technical maintenance updates related to Horizon, to keep Horizon activity visible, structured, and easy for the DAO to track. Context Horizon is Aave’s solution for bringing real world assets (RWAs) onchain, enabling qualified participants to borrow stablecoins, including GHO, against tokenized assets while respecting issuer compliance requirements. It is designed to grow over time, both in the assets it supports and in the underlying implementation. As Horizon matures, it evolves across surfaces spanning price feeds, oracle adapters, permission and access controls, asset configuration, and contract deployments among others. Some updates will be routine maintenance, while others will introduce new functionality or broader initiatives. 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 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 updates, oracle adapter changes, permission and access control alignment, asset configuration maintenance, deployment consistency fixes, address registrations, and other changes required to keep Horizon components aligned with the approved architecture. Where a change should go through the normal governance process, such as new market listings, new collateral onboarding, 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 standalone update here. 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. 3 posts - 1 participant Read full topic