Potential for reentrancy attacks. Some NonReentrant functions are marked external and they in turn call private internal functions which is a known work around for Re-entrancy
The contract uses a non-reentrant modifier for some functions, but not for all. This could potentially lead to reentrancy attacks if not properly managed.
The _revertIfHealthFactorIsBroken(addresss) invariant check at the end of NonReentrant marked functions helps in this regard, similarly to the way Uniswap V2 flashloans work to ensure that everything borrowed is repaid atomically with a fee
This could potentially lead to unexpected behavior or loss of funds. I have not found a way to do this profitably
Manual Verification
Forge and Foundry
It is recommended to use the non-reentrant modifier for all external functions that modify state.
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.