The function claimFees(...) lacks reentrancy protection, posing a risk if future features are introduced.
The function performs token transfers without reentrancy guards.
Although current logic sets the user's fee balance to zero, future changes could introduce risks.
Potential reentrancy attacks if new features or external calls are added.
Manual code review.
Add reentrancy guards to critical functions.
Review future changes for reentrancy risks.
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.