# BGD. Operational oracles update

**URL:** <https://governance.aave.com/t/bgd-operational-oracles-update/13213>\
**Category:** Development\
**Created:** [May 25, 2023, 2:38pm UTC](https://governance.aave.com/t/bgd-operational-oracles-update/13213 "2023-05-25T14:38:03Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![bgdlabs](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/bgdlabs/32/1829_2.png) [@bgdlabs](https://governance.aave.com/u/bgdlabs)\
**Post date:** [October 23, 2023, 7:40am UTC](https://governance.aave.com/t/bgd-operational-oracles-update/13213/13 "2023-10-23T07:40:15Z")

</div>

On the operational side of oracles, in order to keep consistency between Aave v3 and other legacy instances (v2, v2 AMM, v1), we will be creating a proposal to configure the deprecated fallback oracle address to `address(0)` on them.

Even if we don’t recommend doing it in the current form, this doesn’t affect any improvement/re-activation of this mechanism in the future, as it will be possible to set it up again by calling `setFallbackOracle()`.

---

_[View the full topic](https://governance.aave.com/t/bgd-operational-oracles-update/13213)._