What is this about?

The discussion revolves around a series of technical maintenance proposals for the Aave platform, initiated by Bgdlabs¹. These proposals aim to enhance the platform's functionality and security. Notable updates include the deprecation of outdated price feeds, the introduction of fixed price adapters, and the implementation of security features across different Aave versions. The goal is to maintain the platform's integrity and ensure its seamless operation. There is also an emphasis on synchronizing the implementation of the L2 PriceOracleSentinel across networks such as Arbitrum and OP stack to correct discrepancies in L2Sequencer Chainlink feed updates, aiming for a consistent and accurate approach⁸. Additionally, a proposal has been discussed to update the emergency admin address for the deprecated Aave v2 Automated Market Maker (AMM) pool to match the emergency admin addresses of Aave v2 and v3 on Ethereum, which was identified as a necessary change during an internal security review¹⁰.

How is the community reacting?

The community is actively engaged in the discussion, with a three-day forum discussion period followed by the AIP stage, adhering to the standard ARFC + AIP procedure to address concerns¹. Discussions are ongoing, and the community is preparing for the voting phase. Two proposals are expected to go to vote soon⁴. Bgdlabs has proposed aligning the L2 PriceOracleSentinel implementation across networks like Arbitrum and OP stack to prevent unexpected downtime and ensure a harmonized strategy⁸. The community is also considering the proposal to update the emergency admin address for the deprecated Aave v2 AMM pool¹⁰.

Why this is positive?

• The proposals aim to preserve the platform's security and functionality, including the activation of the FreezingSteward smart contract on Aave v3 networks³.
• They address the end of support by Chainlink by phasing out the REP/ETH price feed and introducing a fixed price adapter².
• The proposals promote uniformity across Aave's networks, enhancing user experience and trust in the platform's stability³.
• The harmonization of the L2 PriceOracleSentinel implementation across networks will help prevent unplanned outages and ensure a consistent approach⁸.
• Updating the emergency admin address for the deprecated Aave v2 AMM pool to match other Aave instances on Ethereum simplifies operations and maintains consistency¹⁰.

Why this is negative?

We have not been able to determine whether this will be negative.

Next actions

• Community members are encouraged to review the detailed proposals and engage in the imminent votes, including the deprecation of the REP/ETH price feed on Aave v1 and the activation of the FreezingSteward on Aave v3 networks⁴.
• The proposal that allows the emergencyAdmin to freeze reserves on Aave V2 needs to be considered, in accordance with AIP 361⁵.
• The proposal to replace Chainlink price feeds on Aave v3 Harmony with fixed price adapters due to Chainlink's cessation of Harmony services requires attention⁶.
• Two proposals are prepared for voting, as announced by Bgdlabs. The first allows the emergencyAdmin to freeze on Aave V2, and the second freezes price feeds on v3 Harmony. Community members can participate in these votes through the provided links⁷.
• Bgdlabs has announced the creation of proposal 391, which seeks to standardize the L2 PriceOracleSentinel implementation across all networks. The voting on this proposal is expected to start in about 24 hours⁹.
• The proposal to update the emergency admin address for the deprecated Aave v2 AMM pool is also under consideration, following the internal security review¹⁰.