Executed

Prices operational update. Unify disabled fallback oracles


Proposal ID

351

Proposed

Oct 23rd, 2023

Result details
Final Votes

Quorum

559.44K of 0

Majority support

Yes

For

559.44K

Against

0

Abstain

0

Proposal


title: Prices operational update. Unify disabled fallback oracles author: BGD Labs (@bgdlabs) discussions: https://governance.aave.com/t/bgd-operational-oracles-update/13213/13

Simple Summary

Unify the approach of Aave v1 and Aave v2 fallback oracles with Aave v3: fully disabling it by pointing to address(0), until (if) the community decides to explicitly re-activating them.

Motivation

The fallback oracle is a legacy mechanism, currently deprecated, as reliance on the main oracle (Chainlink) is expected, so there is not really much value on fallback.

Even if currently the community is exploring re-activating the fallback in Aave v3 Optimism, before that, the fallback should be configured on all Aave instances to the null address (address(0)), to be technically fully consistent.

More specifically, this will affect Aave v1 and all the Aave v2 instances on which there is any inactive fallback connected.

Specification

  • call ORACLE.setFallbackOracle(address(0)) to replace the fallback oracle with the null address on Aave v1, Aave v2 and Aave v2 AMM

References

Copyright

Copyright and related rights waived via CC0.

Final Votes

Quorum

559.44K of 0

Majority support

Yes

For

559.44K

Against

0

Abstain

0

Final Votes
Status

Mon Oct 23, 10:23 am

Published onchain

Mon Oct 30, 09:39 am

Voting period started

Thu Nov 2, 01:39 am

Voting period ended

Sat Oct 28, 03:06 am

Proposal executed