The deposit
function accepts a deadline
as an input the parameter which, according to the documentation, "the deadline for the transaction to be completed by". However, this parameter is never actually used. As a consequence, operations that add liquidty to the pool might be executed at unexpected times, in market conditions when the deposit rate is unfavorable.
This also makes this part susceptible to MEV attacks.
Proof of concept: the deadline
parameter is unused (this is highlighted by the compiler too).
Transactions can be sent when market conditions are unfavorable, even when the deadline is set.
Manual review, Foundry.
Perform the following changes to the function:
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.