Aave Labs has outlined a technical maintenance update for Aave Horizon V3 that would replace the current RLUSD and USDC price feeds with capped oracle adapters. Under the proposal, both assets would continue to rely on their respective Chainlink feeds, but each reported price would be limited to a maximum of 1.02.
The update was posted in a new Horizon maintenance thread on Aave’s governance forum, which Aave Labs said is meant to keep lower-scope technical changes visible to the DAO without routing every item through a broader governance discussion. The firm said this type of update is intended for changes that are limited in scope and not expected to trigger material community disagreement.
What the proposal changes
The specific change would update the Aave Horizon V3 oracle configuration for RLUSD and USDC. Rather than using the existing direct price feeds, Horizon would point both assets to newly deployed CAPO price adapters through a setAssetSources call on the Horizon Aave oracle.
According to the post, each adapter would use the corresponding Chainlink oracle as its underlying source while enforcing an upside cap of 1.02. In practice, that means the assets would still track Chainlink pricing, but the reported value on Horizon could not rise above the configured ceiling.
Why capped adapters are being used
Aave Labs said the change follows a recommendation from risk service provider LlamaRisk. The stated rationale is that pricing RLUSD and USDC through capped adapters is preferable to using direct feeds for these assets.
The post added that this approach is already used elsewhere in the protocol for other assets. By wrapping the Chainlink feeds in CAPO adapters, the system is designed to preserve the underlying reference source while constraining upside deviations.
Addresses and technical specification
For RLUSD, the asset address listed in the proposal is 0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD. Its referenced Chainlink feed is 0x26C46B7aD0012cA71F2298ada567dC9Af14E7f2A, and the proposed price adapter is 0x9e7c31e9b3c76ea759d9f7464210353862f0c957, with a cap set at 1.02.
For USDC, the asset address is 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48. The cited Chainlink feed is 0x8fFfFfd4AfB6115b954Bd326cbe7B4BA576818f6, and the proposed adapter is 0x46f94aff8cF7DdC8557eF69f7276087b01C8f363, also capped at 1.02.
How Horizon maintenance updates are meant to work
In the broader thread, Aave Labs described Horizon as Aave’s framework for bringing real-world assets onchain, allowing qualified participants to borrow stablecoins, including GHO, against tokenized assets while meeting issuer compliance requirements. As the system expands, Aave Labs said technical adjustments may cover areas such as price feeds, oracle adapters, permissions, access controls, asset configuration, and deployments.
The company said maintenance items in the thread are reserved for narrow technical updates, while more consequential matters such as new market listings, new collateral onboarding, materially significant risk changes, budgets, or incentives would still go through the usual ARFC, Snapshot, or AIP governance paths. Where an update needs onchain governance, Aave Labs said it will post the item before an AIP is created; in other cases, it may be executed through an authorized operational multisig or Security Council route, with that path explained in the post.
For this RLUSD and USDC oracle change, the immediate next step is execution of the oracle source update if the maintenance item proceeds. Aave Labs presented the proposal in its role as a service provider to the Aave DAO and said the work falls within its approved scope supporting DAO operations.
Source: governance.aave.com