Aave Metis V3

Summary

This proposal allows the Aave governance to activate the Aave V3 Metis pool (3.0.2) by completing all the initial setup and listing WETH, USDC, USDT, DAI, and METIS as suggested by the risk service providers (Gauntlet and Chaos Labs) on the governance forum. All the Aave Metis V3 addresses can be found in the aave-address-book.

Motivation

All the governance procedures for the expansion of Aave v3 to Metis have been finished, said:

• Positive signaling and approval regarding the expansion on the governance forum, temp check snapshot, and final snapshot.
• Positive technical evaluation done by BGD Labs of the Metis network, as described in the forum in detail.
• Positive risk analysis and assets/parameters recommendation by the risk providers Chaos Labs and Gauntlet, as commented on the forum.

Specification

This proposal's payload does the following: grants POOL_ADMIN permissions to all the asset listing Stewards created inside the constructor() of the payload via ACL_MANAGER.addPoolAdmin(stewards[i])

The Steward pattern is taken from V3-listing stewards, already used for the activation of Aave V3 Ethereum. Each Steward will handle the listing of one specific asset and then renounce to the granted POOL_ADMIN role. This process is needed as otherwise, the proposal's gas limit would be really high.

The pool activation will be done via the cross-chain governance with the help of cross-chain forwarder on Ethereum, which on a successful vote by the community, will trigger queuing of the payload action on Metis, which later could be executed by anyone.

Configuration snapshot

What you can see here is a formatted excerpt of the configuration snapshot with the relevant configurations after proposal execution. Although stable borrowing is disabled for all the respective assets, interest rate parameters for stable borrowing have been configured according to the values set in Aave V3 Ethereum. You can find the complete snapshot in the proposal repository.

Reserve Configurations

InterestRateStrategies

Security procedures

The proposal execution is simulated within the tests and the resulting pool configuration is tested for correctness.

The deployed pool and other permissions have been programmatically verified.

In addition, we have also checked the code diffs of the deployed metis contracts with the deployed contracts on Ethereum and other networks.

As a matter of caution, the POOL_ADMIN role will be given for the first weeks to the Aave Guardian multisig.

Deployed Contracts

• ProposalPayload

References

• Discussion: asset listings & parameters
• Code: ProposalPayloadActivation

Copyright

Copyright and related rights waived via CC0.