FeedProjects
Developers
Settings
๐ŸŽ‰ A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
Aave

Insights

Proposals

Discussions

Members

Information

Reports

Create Proposal

Aave

InsightsProposalsDiscussionsMembersInformationReports
Proposal
Back to Proposals
closedEnded 3 years ago ยท Snapshot (Offchain)

[ARFC] Aave Robot v1 activation

By 0xf71f...c61E02

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:

  1. A technical service provider (BGD in this case) will deploy both the Robot smart contracts and the AaveCLRobotOperator, on each supported network.
  2. 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.

Continue Reading
Connect Wallet to Add Note
0
Votes 2109
VoterCast PowerVote & Rationale
0x329c...543eD4
233,390

For

FranklinDAO (Prev. Penn Blockchain)
108,948

For

0x62a4...96816a
82,848

For

0x13BD...138548
81,789

For

0xB83b...Fbcf5C
81,413

For

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Thu June 29 2023, 03:05 pmVoting Period Starts
  • Sun July 02 2023, 03:05 pmEnd Voting Period
Current Results

1-For

745,131.815

99.99%

2-Abstain

81.618

0.01%

3-Against

27.347

0%
Quorum 745,240.78/320,000
DocumentationBrandingContact Us