Missing slippage control in priorityPool:deposit()
Users can be frontrun and receive a worse exchange rate from assetToken to shares
than expected when they initially deposit the assetToken using priorityPool:deposit().
There's no protection at all, no minimum return amount or deadline for the trade transaction to be valid which means the trade can be delayed by miners or users congesting the network, as well as being sandwich attacked - ultimately leading to loss of user funds.
Deposits can be sandwich attacked causing massive loss to the user
Manual Review
Allow user to specify min amount of shares received from priorityPool:deposit()
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.