Technical maintenance proposals

a.DI/Governance. Enable support for Plasma


Simple Summary

Proposal to register the necessary Plasma adapters on a.DI, a technical pre-requirement for an activation vote of Aave v3 Plasma.


Motivation

In order to be able to pass messages from Ethereum to Plasma via a.DI (Aave Delivery Infrastructure), it is necessary to at least have three valid adapters Ethereum → Plasma smart contracts enabled in the system.

The first case of message passing Ethereum → Plasma is the activation proposal for an Aave v3 Plasma pool, and, to be able to execute the payload on on the Plasma side, the Aave governance should approve in advance the a.DI adapters smart contracts.

This procedure mirrors the requirements of previous networks like Sonic or Celo.


Specification

The proposal payload simply registers pre-deployed Plasma adapters (with the necessary configurations to communicate with the Plasma a.DI) on the Ethereum a.DI instance.

This is done by calling the enableBridgeAdapters() function on the Ethereum Cross-chain Controller smart contract.

The optimal bandwidth on the Ethereum → Plasma path is set to 2 by calling updateOptimalBandwidthByChain().

The following are the configured adapters for the Ethereum → Plasma path. The required confirmations on the path are 2 out of 3.



The new a.DI deployments on Plasma network are as follows:

Contract Address
CrossChainController 0x643441742f73e270e565619be6DE5f4D55E08cd6
Granular Guardian 0x60665b4F4FF7073C5fed2656852dCa271DfE2684
Chainlink Emergency Oracle 0xF61FE74Ec1cFbd9Ee8Bd27592D2EDEe0E2aA85Cf

The new Aave Governance deployments on Plasma network are as follows: