The TSwapPool::deposit function fails to enforce the deadline parameter, allowing transactions to complete after the specified deadline.
The deposit function in the TSwapPool contract includes a deadline parameter intended to specify the time by which a transaction should be completed. However, this parameter is currently not enforced within the function's logic. As a result, transactions can be processed even after the specified deadline, potentially leading to liquidity being added at unfavorable market conditions.
Due to the absence of deadline enforcement in the deposit function, transactions can execute when market conditions are unfavorable for liquidity provision, despite the inclusion of a deadline parameter. This undermines the intended control over transaction timing and liquidity management.
Manual code review
you can integrate the existing revertIfDeadlinePassed modifier. Here's how you can modify the deposit function to enforce the deadline check:
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.