The constructor in AaveDIVAWrapper
contract, does not use the expected order
of arguments defined in AaveDIVAWrapperCore
. Leading to incorrect initialization
of _diva
and _aaveV3Pool
state variables.
AaveDIVAWrapper
is initialized with the following arguments:
But, if we check AaveDIVAWrapperCore
, the first argument is the address of the diva_
protocol and the second argument is the address of `aaveV3Pool` .
In first place, this will cause to redeploy the contract as there's no implemented setters to change this state variables. Furthermore, registerCollateralToken()
will always revert in this case and render the contract unusable.
Manual analysis.
Use the correct order of arguments in the constructor of AaveDIVAWrapper
.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.