a.DI ZkSync path activation

Share on X
Raw-Ipfs
For

862.16K

Against

0

Voters

Voting power

Support

aci.eth

374.77K

For

ezr3al.eth

224.13K

For

areta...v.eth

103.58K

For

0x2cc...54Df1

46,218.39

For

winte...e.eth

44,707.69

For

Payload
Show more
Created

9 Aug 2024, 8:58 AM

Open for voting

10 Aug 2024, 9:16 AM

Voting closed

13 Aug 2024, 9:16 AM

Passed

Finished

14 Aug 2024, 9:38 AM

Executed

a.DI ZkSync path activation

Created

9 Aug 2024, 8:58 AM

Open for voting

10 Aug 2024, 9:16 AM

Voting closed

13 Aug 2024, 9:16 AM

Passed

Finished

14 Aug 2024, 9:38 AM

Executed

Author

BGD Labs @bgdlabs

Creator

0xf71fc92e2949ccF6A5Fd369a0b402ba80Bc61E02

Copy

Simple Summary

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

Motivation

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

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

This procedure mirrors the requirements on previous networks like Scroll.

Specification

The proposal payload simply registers a pre-deployed ZKSync adapter (with the necessary configurations to communicate with the ZKSync 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 new a.DI deployments on ZkSync network are as follows:

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

References

Copyright

Copyright and related rights waived via CC0.

by BGD Labs