Simple Summary

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

Motivation

In order to be able to pass messages from Ethereum to Bob via a.DI (Aave Delivery Infrastructure), it is necessary to at least have one valid adapter Ethereum → Bob smart contract enabled in the system (native adapter).

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

Specification

The proposal payload simply registers pre-deployed Bob adapters (with the necessary configurations to communicate with the Bob 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 following are the configured adapters for the Ethereum → Bob path. The required confirmations on the path are 1 out of 1.

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

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

References

• Adapter Implementations: Bob Native Adapters
• Payload Implementation: Payload
• Payload Tests: tests
• Diffs: a.DI diffs
• Discussion

Copyright

Copyright and related rights waived via CC0.