Incorrect order of arguments of AaveDIVAWrapperCore::constructor call at AaveDIVAWrapper::constructor. Which results in smart contract being deployed in a broken state.
The order of arguments of the AaveDIVAWrapperCore::constructor is (address diva_, address aaveV3Pool_, address owner_), but AaveDIVAWrapper calls it with a different order of arguments: (_aaveV3Pool, _diva, _owner). Which is a bug.
Since the protocol assumes the use of AaveDIVAWrapper in permissionless maner, this will result in smart contracts being deployed in an inoperative state when deployed by external developers.
Foundry
Manual review
Foundry
First. The order of arguments in the call of AaveDIVAWrapperCore::constructor must be corrected.
Second. The order of arguments in the AaveDIVAWrapper::constructor must be consistent in all places in the code where these parameters are accepted or returned.
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.