[ARFC] Aave Robot v1 activation

Voting ended over 2 years agoSucceeded

title: [ARFC] Aave Robot v1 author: @bgdlabs - BGD Labs (Bored Ghosts Developing) created: 2023-06-28

Summary

Request approval from the community to move forward Aave Robot v1, the first iteration of a framework and architecture of smart contracts to automate permissionless actions of Aave, like those related to the Aave governance v2; powered by Chainlink Automation.

How will it work?

A detailed description of the system can be found on the Aave governance forum, but as summary:

Multiple Robot smart contracts will be deployed, that will contain the logic to 1) understand when a permissionless action on Governance v2 (or cross-chain governance) can be triggered (queueing, execution, cancel) and 2) execute them.
A AaveCLRobotOperator will be deployed on each network, that will allow for the DAO to have "admin" control on all the underlying robots, in order to register new ones, cancel or funding them with the LINK required for execution.
To simplify operational complexity, the maximum gas limit proposed will be close to the maximum allowed by the underlying Chainlink infrastructure. As anybody can top-up LINK on the Aave Robot via a permissionless function on the AaveCLRobotOperator, the community could request for external entities to partially or totally cover the execution costs of proposals by using it.
As in some cases it could be desirable for example to disable automation of a specific proposal and this is not possible with "slow" governance procedures, a Robot Guardian role is defined that will be able to 1) disable automation for a certain governance proposal and 2) "pause" automation on a specific network. Both actions are non-invasive, as it only affects the automation system, not the underlying governance system at all. Initially, BGD will keep the Robot Guardian role.

Setup flow

For the DAO to activate the system the procedure is simply the following:

A technical service provider (BGD in this case) will deploy both the Robot smart contracts and the AaveCLRobotOperator, on each supported network.
A governance proposal will be submitted to activate and configured those robots, and top them up with LINK from the Aave Collector.

Afterwards, the DAO can register new robots via governance proposal, or manage the registered ones however needed.

Off-Chain Vote

For

745.13K AAVE100%

Against

27.35 AAVE0%

Abstain

81.62 AAVE0%

Quorum:233%

Download mobile app to vote

Timeline

Jun 28, 2023Proposal created

Jun 29, 2023Proposal vote started

Jul 02, 2023Proposal vote ended

Dec 25, 2025Proposal updated

How will it work?

A detailed description of the system can be found on the Aave governance forum, but as summary:

Multiple Robot smart contracts will be deployed, that will contain the logic to 1) understand when a permissionless action on Governance v2 (or cross-chain governance) can be triggered (queueing, execution, cancel) and 2) execute them.

A AaveCLRobotOperator will be deployed on each network, that will allow for the DAO to have "admin" control on all the underlying robots, in order to register new ones, cancel or funding them with the LINK required for execution.

To simplify operational complexity, the maximum gas limit proposed will be close to the maximum allowed by the underlying Chainlink infrastructure. As anybody can top-up LINK on the Aave Robot via a permissionless function on the AaveCLRobotOperator, the community could request for external entities to partially or totally cover the execution costs of proposals by using it.

As in some cases it could be desirable for example to disable automation of a specific proposal and this is not possible with "slow" governance procedures, a Robot Guardian role is defined that will be able to 1) disable automation for a certain governance proposal and 2) "pause" automation on a specific network. Both actions are non-invasive, as it only affects the automation system, not the underlying governance system at all. Initially, BGD will keep the Robot Guardian role.

Setup flow

For the DAO to activate the system the procedure is simply the following:

A technical service provider (BGD in this case) will deploy both the Robot smart contracts and the AaveCLRobotOperator, on each supported network.

A governance proposal will be submitted to activate and configured those robots, and top them up with LINK from the Aave Collector.

Afterwards, the DAO can register new robots via governance proposal, or manage the registered ones however needed.