Closed lekhovitsky closed 1 month ago
@lekhovitsky
allowAdapter
natspec should be updated because now the function does not (or at least not directly) reverts if adapter
or adapter
's targetContract
are equal to the creditManager
because this check is performed directly inside the CreditManagerV3(creditManager).contractToAdapter(...)
call
@lekhovitsky
allowAdapter
natspec should be updated because now the function does not (or at least not directly) reverts ifadapter
oradapter
'stargetContract
are equal to thecreditManager
because this check is performed directly inside theCreditManagerV3(creditManager).contractToAdapter(...)
call
I do agree that natspec could be updated to at least state that the check is performed indireclty as the check is now only performed inside the CreditManagerV3(creditManager).setContractAllowance
function which does follow the recommendation of issue https://github.com/spearbit-audits/review-gearbox/issues/61 by removing the check under the configurator due to duplications on the CreditManagerV3
.
@StErMi @cryptarasecurity It's fine for user-facing contracts like credit configurator or credit facade to make comments about checks or other actions performed in the credit manager, so decided not to update the comment.
@lekhovitsky the TargetContractNotAllowedException
used in allowAdapter
is not entirely correct because the function reverts if the target contract OR the adapter are equal to the CreditFacade
. The same would be for the setCreditFacade
function.
For the rest, the PR seems to fix/address all the linked issues linked above.
@StErMi Exception names are quite a mess but fixing them all consistently again creates a huge diff which nobody would want to review, so keeping those as is
Fixes:
Acknowledges: