If the tillIn function transfers tokens, there is a potential for a reentrancy attack, where an attacker could recursively call the function to drain tokens.
A malicious contract could exploit a reentrancy vulnerability by calling the tillIn function in a recursive manner to deplete the capital pool
This could result in significant financial loss as the pool could be drained by the attack.
Manual review
CODE SNIPPET
Use the Check-Effects interactions pattern, or integrate OpenZeppelin's ReentrancyGuard.
Invalid, all [vague generalities](https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity#vague-generalities) talking about possible reentrancies 11and afaik, reentrancy is not possible and not proven.
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.