Ernesto Boado

- [x] AIP text - [ ] Links to resources

## Context The problem/consequences are explained [HERE](https://governance.aave.com/t/bgd-aave-v2-ethereum-fei-security-report/10251). ## How Having a 100% RF is a legitimate configuration for a reserve, so the fix should be on the logic not properly...

Fix for #315 (Aave v2 Avalanche)

1

Same exact changes as on https://github.com/aave/protocol-v2/pull/316 but to apply on the deployment of Aave v2 Avalanche. Only non-solidity code was slightly adapted to the version of the repo from where...

Fix for #315 (v2 Ethereum)

1

Same exact changes as on https://github.com/aave/protocol-v2/pull/316 but to apply on the deployment of Aave v2 Ethereum. Only non-solidity code was slightly adapted to the version of the repo from where...

Fix for #315 (v2 Polygon)

1

**Changes** - On `updateState()` of `ReserveLogic`, add a condition to not do any update if the timestamp has not changed since the last stored on the reserve's data. This is...

On the init command, scaffold the subgraph with the contracts names of the ABIs

5

Currently the execution of `graph init` generates ABI's with the name **Contract** because of this https://github.com/graphprotocol/graph-cli/blob/3a9a5a972795029b63843761171fd7687e12fd8f/src/commands/init.js#L190 Could be good to apply take as name the filename of the ABI instead...