https://app.aave.com/governance/proposal/?proposalId=134
https://governance.aave.com/t/update-renfil-interest-rate-strategy-on-aave-v2-ethereum/11049
🔧 📊 params-update
This proposal minimizes the interest rate parameters of renFIL on Aave v2 Ethereum, by replacing its rate strategy contract.
Transaction: https://etherscan.io/tx/0x29c79a00f935948dfd3dff560212e6634fc20eb09e30c4904fb015333cd46935
- id: 134
- creator: 0xf71fc92e2949ccf6a5fd369a0b402ba80bc61e02
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0xbfcf7a2d4a91e91c72cdcf07ec65de6bf507daab]
- values: [0]
- signatures: [execute()]
- calldatas: [0x]
- withDelegatecalls: [true]
- startBlock: 16233437
- endBlock: 16252637
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x6e0d5a583e556e7bd8d1b9e3456b34ac085539320e248446792ea3600af12af0
There seems to be some infrastructure problem on Tenderly, which causes the state transitions to show erroneously (aTokenAddress instead of the correct interestRateStrategyAddress). We have double checked both payload code and events emitted, and everything seems correct
This proposal has been created by BGD Labs, so we find more appropriate to describe what exactly the the proposal's payload does:
- The payload calls the Pool Configurator of Aave v2 Ethereum to set as rate strategy of renFIL THIS ONE.
- The new rate strategy return zero value for all external functions, which as explained on the repository of this project, doesn't cause any problem to the protocol.
✅ 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.