Is there any risk here given the last audit in the Aave v2 contracts was in early 2021?
- undefined Aave
I was looking through the Aave v2 contracts and noticed the `WrappedTokenGatewayV2 `was launched in Sept. 2022. Is there any risk here given the last audit was in early 2021?
This [commit](https://github.com/aave/aave-v3-periphery/commit/74d27ee7079c8e16dee52cd4cb59cae2bb5846e0) contains the change, it moves the Pool address from a parameter to the constructor, to prevent someone from injecting their own pool contract and transferring tokens in case someone accidentally sent them directly to this contract.