Simple Summary

Proposal to migrate existing Aave robots from chainlink automation v1.2 to v2.1. For governance v3 robots on ethereum, we introduce gas-capped robots in order to limit execution based on network gas price. We also activate robots for refreshing liquidity mining rewards for static-a-tokens.

Motivation

With the release of Chainlink automation v2.1, we think its a good idea to update the Aave Robot existing infrastructure to the latest v2.1 version. In addition, as an effort to reduce the cost spent in gas in times of high gas prices, we also introduce gas-capped robots on mainnet which will be activated via this proposal.

Currently when a liquidity mining reward is added after static-a-token creation, it needs to be registered manually on the token via the permissionless refreshRewardTokens() method. As this process is not currently automated users might be missing out on rewards until the method is called, so now we introduce the robot for static-a-token to automate this process.

Specification

For the migration, the robots registered on the previous robot operator contract will be cancelled and new robots will be registered using an updated robot operator contract, compatible with the newer version of chainlink automation v2.1.

The robots will be cancelled by calling the cancel() method by the payload on the previous robot operator contract, and after the delay has passed anyone could call the permissionless method withdrawLink() on the robot operator contract to withdraw the unused funds on the previous robots to the collector.

On the newer robot operator, the payload will call the register() method to register the keepers with the newer chainlink automation registry supporting v2.1.

The proposal also refills the cross-chain-controller contract (part of aDI) on mainnet with 1 ethereum from the collector.

Note: All aave governance v3 robots along with robots used for gsm swap freeze and Proof of Reserve will be migrated via this proposal and will use the same contract as before except the one's mentioned below

References

• Implementation: AaveV2Polygon, AaveV2Avalanche, AaveV3Ethereum, AaveV3Polygon, AaveV3Avalanche, AaveV3Optimism, AaveV3Arbitrum
• Tests: AaveV2Polygon, AaveV2Avalanche, AaveV3Ethereum, AaveV3Polygon, AaveV3Avalanche, AaveV3Optimism, AaveV3Arbitrum
• Discussion

Copyright

Copyright and related rights waived via CC0.