BGD. Technical maintenance proposals

a.DI update: CCIP bridge adapters and CCC (CrossChainController)


Simple Summary

Technical maintenance proposal to update the CrossChainController and CCIP Bridge Adapters components of a.DI (Aave Delivery Infrastructure).


Motivation

Set of minor improvements on the CrossChainController smart contract to ease and standardise off chain tracking of a.DI contracts and events; and update of the Chainlink CCIP Bridge Adapter to be compatible with the new CCIP version.


Specification


Bridge adapters

On this side, the CCIP Bridge Updated is updated to have full compatibility with CCIP v1.2.0. This affects Ethereum, Polygon PoS, BNBChain and Avalanche.


Cross-chain controller (CCC)

On the CrossChainController (CCC) implementation, we have updated the logic so that all bridged messages will be treated the same even if required confirmation have already been reached (previously these messages where ignored in practise).



Security

The updates has been reviewed by Certora, the engaged security provider of the Aave DAO.


References

5 Likes

We have created an on-chain AIP for this proposal.

Voting will start in approximately 24 hours, participate :ghost:
https://vote.onaave.com/proposal/?proposalId=53

3 Likes

We have created an on-chain AIP for this proposal.

Voting will start in approximately 24 hours, participate :ghost:

https://vote.onaave.com/proposal/?proposalId=56

2 Likes

Hello BGD, the GUI for the Harmony markets and dashboards pages is no longer displaying relevant data. Can you confirm its just the GUI not functioning, and should collateral asset repeg happen, we the lenders, can get our funds back?

1 Like

Hello @Tobes . We are not in charge of app.aave.com, but the team maintaining it (Aave Labs) has confirmed the issue is related with fetching the data from from the Harmony network, because as Chainlink deprecated support for the network, some helper smart contracts should be adapted.
That doesn’t have any implication on the core Aave pool itself.

2 Likes

a.DI. Native bridge adapters update


Simple Summary

This proposal updates the Native bridge adapters used on a.DI, to add extra naming metadata and make the gas limit configurations more granular.


Motivation

For the past month with a.DI in production, we have noticed small improvements due to the specific mechanics of each bridge provider. Additionally, as we improve the off-chain systems (e.g. monitoring) surrounding a.DI, sometimes it is simply better to add features to the smart contracts to facilitate this off-chain infrastructure.


Specification

Updates the Native bridge adapters used to connect between networks to add Adapter Name to the contracts and provider specific gasLimit configuration

Code diffs for the different networks can be checked on a.DI diff repository for revision 2.
Adapter diffs: Native Adapters, BaseAdapter, IBaseAdapter


Security

The updates has been reviewed by Certora, the engaged security provider of the Aave DAO.


References

3 Likes

We have created an on-chain AIP for this proposal.

Voting will start in approximately 24 hours, participate :ghost:

https://vote.onaave.com/proposal/?proposalId=70

4 Likes

POOL_ADMIN renounceRole() by Guardian on v3 Scroll

Simple Summary

After some maturity time, it is perfectly safe for the Aave Guardian to renounce the POOL_ADMIN role on the newest pool: Aave v3 Scroll.

Motivation

Whenever Aave expands to a new network, this is done in a fully decentralised way via an on-chain governance proposal (e.g. Aave v3 BNB Chain).
Major permissions (upgradeability) of the pool are set to the Aave governance from day 0, but the POOL_ADMIN is given to the Aave Guardian during a period of time for security, even if almost never exercised.
From a technical/security perspective, we don’t see any risk at the moment or need for the Guardian to hold this role anymore, so we will coordinate with its members to renounce on the only applicable pool: Aave v3 Scroll.

Specification

This proposal doesn’t require any governance procedure (Snapshot, on-chain), as the renounce is done directly by the Guardian.

The Aave Guardian (Safe) on Scroll will call the renounceRole() function for the POOL_ADMIN and their own address.

1 Like

LayerZero bridge adapter update to V2


Simple Summary

This proposal updates the LayerZero bridge adapters used on a.DI to connect Ethereum with Polygon, Avalanche, Binance and Gnosis to the new LayerZero V2 version.


Motivation

Since the activation of a.DI in production, LayerZero one of its underlying cross-chain communication providers has updated its infrastructure to version 2.
This proposal replaces the a.DI LayerZero adapter with the new version.


Specification

Updates the LayerZero bridge adapters used to connect between networks to LayerZero V2 and, similar to what has been done on proposal 56 for CCIP, adds an adapter name metadata to the smart contract, to facilitate off-chain tracking.

2 Likes

CAPO on v2 and misc oracles maintenance


Simple Summary

This proposal activates the correlated-assets price oracle (CAPO) system for fiat-pegged stable coins on Aave V2 pools, and does extra miscellaneous updates on price feeds of Aave v2.


Motivation

To continue enhancing the security of the protocol using CAPO and to align with the recent approved proposal for Aave v3, we are introducing the activation of CAPO adapters for Aave v2 pools. As no LSTs are listed on the v2 (stETH is not applicable), we are only applying the adapters to the fiat-pegged stablecoins.

This proposal also includes an update of the oracle for DPI from DPI / ETH to DPI / USD.


Specification


Oracles will be updated using ORACLE.setAssetSource() method. Below is the list of assets per network to be updated:


All assets affected

Network Stables
Mainnet USDC, USDT, DAI, USDP, sUSD, FRAX, GUSD, LUSD, BUSD, TUSD, UST, DPI
Avalanche USDC.e, USDT.e, DAI.e
Polygon USDC.e, USDT, DAI

CAPO configurations

Asset Cap
USDC 4%
USDT 4%
DAI 4%
USDP 4%
sUSD 4%
FRAX 4%
LUSD 10%
BUSD 4%
TUSD 4%
UST 4%

Misc specifications

1 Like

Hyperlane bridge adapter update to V3


Simple Summary

This proposal updates the bridge Hyperlane bridge adapters used on a.DI to connect Ethereum with Polygon, Avalanche, Binance and Gnosis to the new Hyperlane V3 version.
Additionally, removes old native bridges on Optimism, Base, Arbitrum, Scroll and Metis, after verifying that the new active versions work properly.


Motivation

The main motivation of this proposal is to bring the Hyperlane bridge adapters to the up to date version (V3).


Specification

Updates the Hyperlane bridge adapters used to connect between networks to Hyperlane V3 and it also adds Adapter Name to the contracts to make it easy to track off chain

  • To add the new forwarder adapters the function enableBridgeAdapters() will be called on the CrossChainController on the sender side, and allowReceiverBridgeAdapters() on the recipient side.
  • To remove the old forwarder adapters, the function disableBridgeAdapters() will be called on the CrossChainController on the sender side, and disallowReceiverBridgeAdapters() on the recipient side.

The old native receiver bridge adapters to remove are:

2 Likes

Following the recommendation from risk providers to freeze different stablecoins on this post, we proceeded with the creation of the on-chain AIP for CAPO on v2 assets, as it will introduce extra solid protection.

Voting will start in approximately 24 hours, participate :ghost:

https://vote.onaave.com/proposal/?proposalId=82

5 Likes

We have created an on-chain AIP for this proposal.

Voting will start in approximately 24 hours, participate :ghost:

https://vote.onaave.com/proposal/?proposalId=83

3 Likes

We have created an on-chain AIP for this proposal.

Voting will start in approximately 24 hours, participate :ghost:

https://vote.onaave.com/proposal/?proposalId=92

We can confirm the Aave Scroll Guardian has renounced the POOL_ADMIN role.

3 Likes

Aave Robot migration to Chainlink Automation v2 and gas-price optimization


Simple Summary

Proposal to migrate existing Aave robots from chainlink automation v1.2 to v2.1. For governance v3 robots on Ethereum, we also introduce gas-capped robots in order to limit execution based on network gas price.


Motivation

With the release of Chainlink automation v2.1, we think its a good idea to update the Aave Robot existing infrastructure to the latest v2.1 version.
In addition, as an effort to reduce the cost spent in gas in times of high gas prices, we also introduce gas-capped robots on mainnet which will be activated via this proposal.


Specification

For the migration, the robots registered on the previous robot operator contract will be cancelled and new robots will be registered using an updated robot operator contract, compatible with the newer version of chainlink automation v2.1.

The robots will be cancelled by calling the cancel() method by the payload on the previous robot operator contract, and after the delay has passed anyone could call the permissionless method withdrawLink() on the robot operator contract to withdraw the unused funds on the previous robots to the collector.

On the newer robot operator, the payload will call the register() method to register the keepers with the newer chainlink automation registry supporting v2.1.

Note: All aave governance v3 robots along with robots used for gsm swap freeze will be migrated via this proposal

Deployed Gas Capped Robots
Gas Capped Governance Robot 0x1996c281235D99bB3c6B8d2afbEb8ac6c7A39C11
Gas Capped Voting Robot 0x7Ed0A6A294Cf085c90917c0ee1aa34e795932558
Gas Capped Execution Robot 0xBa37F9eDC52f57caFA3a13ddfD655797Cc4FE257
4 Likes