From 54631b179acb3765c2df8b272e7f28b737e0221d Mon Sep 17 00:00:00 2001 From: sendra Date: Wed, 24 Jan 2024 09:50:26 +0100 Subject: [PATCH] Update src/20240122_AaveV3Ethereum_RegisterADIScrollAdapter/RegisterADIScrollAdapter.md Co-authored-by: Ernesto Boado --- .../RegisterADIScrollAdapter.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/20240122_AaveV3Ethereum_RegisterADIScrollAdapter/RegisterADIScrollAdapter.md b/src/20240122_AaveV3Ethereum_RegisterADIScrollAdapter/RegisterADIScrollAdapter.md index 1f26aafcc..e5970e7fa 100644 --- a/src/20240122_AaveV3Ethereum_RegisterADIScrollAdapter/RegisterADIScrollAdapter.md +++ b/src/20240122_AaveV3Ethereum_RegisterADIScrollAdapter/RegisterADIScrollAdapter.md @@ -10,8 +10,11 @@ Proposal to register the scroll adapter on Ethereum a.DI ## Motivation -For the Aave DAO to have control of the Aave Protocol deployed in the Scroll network, a Scroll adapter needs to be -registered in the Ethereum a.DI that is configured for the communication with the Scroll network a.DI. +In order to be able to pass messages from Ethereum to Scroll via a.DI (Aave Delivery Infrastructure), it is necessary to at least have one valid adapter Ethereum -> Scroll smart contract enabled in the system. + +The first case of message passing Ethereum -> Scroll is the activation proposal for an Aave v3 Scroll pool and consequently, to be able to execute on the Scroll side the payload, the Aave governance should approve in advance the a.DI adapter smart contract. + +This procedure was not required on previous activations like BNB, given that their adapter were pre-configured on the initial a.DI release, but will be needed going forward. ## Specification