The current implementation does not have reentrancy guards. While the claimFees() and claim() functions don't seem to directly be at risk due to their straightforward logic and the use of the safeTransfer() from OpenZeppelin (which mitigates some of these concerns), it's generally good practice to prevent reentrancy for any state-changing external functions.
Use the nonReentrant modifier from OpenZeppelin's ReentrancyGuard utility, especially in functions dealing with token transfers or ether withdrawals.
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.