Executed

Activate Proof of Reserve


Proposal ID

402

Proposed

Dec 12th, 2023

Result details
Final Votes

Quorum

563.4K of 0

Majority support

Yes

For

563.4K

Against

0

Abstain

0

Actions

Function 1:

0x000000000000000000000000000000000000000000000000000000000000a86a00000000000000000000000000000000000000000000000000000000000000010000000000000000000000001140cb7cafacc745771c2ea31e7b5c653c5d0b800000000000000000000000000000000000000000000000000000000000000009
Value:0

Proposal


title: "Activate Proof of Reserve" author: "BGD Labs (@bgdlabs)" discussions: "https://governance.aave.com/t/bgd-technical-maintenance-proposals/15274/11"

Simple Summary

This proposal aims to add Proof of Reserve Admin role to the Avalanche V2 Pool Configurator in order to activate the proof of reserve mechanism.

Motivation

At the moment, in Aave v3 Avalanche there are multiple assets with a “bridged” nature: DAI.e, USDC.e, USDT.e, AAVE.e, LINK.e, WBTC.e, BTC.b and WETH.e.

These assets have 2 sides: one deposit account in the network where the asset originated (Ethereum in the case of the *.e assets) and a token smart contract on the “usage” chain (Avalanche in this case).

Given that architecture, there are 2 main attack vectors to exploit “bridged” assets:

An exploit on the usage network, generally minting tokens that have no backing on the origination network, usually called an “infinite minting attack”. An exploit on the origination network, extracting tokens from the deposit contract.

In order to prevent the 1) type of attack Proof of Reserve mechanism was introduced and activated for the V3 Pool on Avalanche almost a year ago. Now we are ready to activate it for the V2 as well.

Specification

  • AaveV2Avalanche.POOL_ADDRESSES_PROVIDER.setLendingPoolConfiguratorImpl() will be called with the new configurator address passed.

  • AaveV2Avalanche.POOL_ADDRESSES_PROVIDER.setAddress() will be called to set proof of reserve executor as the admin.

References

Copyright

Copyright and related rights waived via CC0.

Final Votes

Quorum

563.4K of 0

Majority support

Yes

For

563.4K

Against

0

Abstain

0

Final Votes
Status

Tue Dec 12, 02:56 pm

Published onchain

Tue Dec 19, 07:23 am

Voting period started

Thu Dec 21, 11:23 pm

Voting period ended

Sun Dec 17, 07:49 am

Proposal executed