Both StrategyArb.sol and StrategyOP.sol use swap methods from different decentralized excahnges, both require a deadline and it's set to block.timestamp
however this offers no protection to MEV.
Using block.timestamp
is MEV exploitable because whenever the block builder decides to include the txn in a block, it will be valid at that time, since block.timestamp
will be the current timestamp. more on this issue
Malicious MEV actors can reorganize the transaction to their own benefit extracting value from it.
Manual review.
A specific timestamp should be passed to the function instead of block.timestamp
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.