https://app.aave.com/governance/proposal/?proposalId=129
https://governance.aave.com/t/arc-strategy-on-sunsetting-of-aave-v1/9450
🧊 freeze-asset
This proposal freezes all assets for the Aave v1 and Aave v1 AMM pools, in order to progress with the sunset of v1 instances of the protocol.
Transaction: https://etherscan.io/tx/0x3c840193e9bac84b98012de3f5a3d0bb9dbfa90a901c60c59b233297ef0e1962
- id: 129
- creator: 0xf71fc92e2949ccf6a5fd369a0b402ba80bc61e02
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x6f02253c80a041a773efa35c98d4bc14a0f6ef9e]
- values: [0]
- signatures: [execute()]
- calldatas: [0x]
- withDelegatecalls: [true]
- startBlock: 16140168
- endBlock: 16159368
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x02e04de8258c1dca9c4c6099d8ac2142f1f2833bad5a7ca4154a12aa8f4dd548
This proposal has been created by BGD Labs, so we find more appropriate to describe what exactly the payload does:
- Fetches the addresses of all listed assets on both the v1 and v1 AMM pools.
- For each asset of each pool, call
freezeReserve()on the respective Pool Configurator contract, fetched from each addressed provider.
In terms of security procedures, we have:
- Verified that addresses (pool addresses providers) are correct.
- Test in a Ethereum fork environment that, after simulating the execution of the payload, all assets are frozen, HERE.
- Simulation the execution on a fork environment and checking on an Aave v1 UI that effectively, the assets appear as frozen.
The proposal is really simple, so we don't consider any extra security review was necessary.
✅ The code on the proposal payload corresponds to the proposal specification.
✅ The proposal includes a proper tests suite, checking all necessary post-conditions.
✅ Only one payload used via delegatecall
✅ BGD wrote the payload.
❌ With BGD writing the payload, at least another party reviewed it.