Aave Bridge: How to Apply governance results on Ethereum to multiple networks

Aave Cross-chain Governance Bridge: How to Apply Governance Results on Ethereum to Multi-chain in 3 Minutes

Karen, Link News

While most DeFi projects on Ethereum gradually seek to expand to multi-chain, the importance of cross-chain governance is often ignored. How to complete governance activities on Ethereum and apply the results to other networks is a problem that all applications with multi-chain layout or planning to expand to multi-chain must face. Last week, Aave officially announced plans to roll out a cross-chain governance bridge and made public its cross-chain codebase to enable true cross-chain governance on Ethereum.

Before formally introducing Aave cross-chain governance bridge, it is necessary for us to understand AaveThe governance structureIn the Aave community governance process, the community creates an Aave improvement proposal (AIP), and after discussion and agreement, submits it to the chain for token holders to vote on governance. In addition, as an initial safeguard against the agreement, the guardian account controlled by the community with multiple signatures can cancel the proposal before it is implemented. There are two main components in the concrete governance process:

Master governance contract, which allows users to create proposals and, in addition, AAVE holders to vote on those proposals;

The executor contract, if the proposal is passed, will implement and execute any proposal approved by the AAVE holder through time lock and define the implementation parameters for each particular proposal.

Aave governance architecture

If a project is multi-chained, decisions made through governance on the Ethereum network can be applied to other networks using a bridge between the two networks.

Bridge Executor contracts play a central role in Aave governance cross-chain tools. The Aave Polygon market, for example, is still controlled by multiple signatures, but with governance cross-chain tools, once the governance process on Aave on Ethereum is approved, the bridge performer contract facilitates a range of operations on other chains, including queuing, latency, and execution logic. The specific process is:

On the Ethereum side, the system receives proposal data from the Aave governance executive;

On the Polygon side, the system receives proposal data bridged from the Ethereum side;

After an extra time lock window, the proposal is executed on Polygon.

Aave Polygon Cross-chain Governance Architecture diagram

For specific technical details, please refer tohttps://github.com/aave/governance-crosschain-bridges.

Aave has submitted a test for cross-chain governance workflowsThe proposal, hoping to prove the feasibility of controlling the Aave Polygon market through Aave Ethereum governance. If the proposal is approved on Ethereum, a cross-chain message is posted to the Polygon network, where the bridge executor receives it and queues it up, and the Guardian address has three days to cancel the proposal, after which the proposal can be implemented on Polygon.

Of course, the current test proposal does not make material changes to the current Aave Polygon market ecosystem or any other deployment of the Aave protocol, but is merely a test of the cross-chain workflow. In addition to Polygon, currently the Aave cross-chain bridge repository also supports bridging to Arbitrum, however, Aave does not yet support Arbitrum.

  Aave Arbitrum cross-chain governance architecture diagram

Of note, Aave open-source the cross-chain governance bridge code base, allowing anyone to build their own cross-chain bridge. The governance bridge also passed the MixBytes audit. In addition, Aave has opened source its front-end user interface and UI cache server and user interface toolkit.

With the deployment of the cross-chain governance bridge, Aave may open a new paradigm for cross-chain governance for other projects. Of course, Aave continues to explore multi-chain strategies. Earlier this month, Aave founder Stani Kpechov was at Chainpnk's Smart Contract Summitsaid, and consider expanding its market beyond Ethereum and Polygon. Kpechov said it is likely to deploy Neon Labs' Solana EVM compatibility solution on Solana, and is exploring deployment on Networks such as Avalanche and Optimism.

The original link

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia