Using block.timestamp as the expiration or deadline for an operation doesn't imply "require immediate execution"; instead, it indicates "I am comfortable with the timestamp of the block in which this transaction appears." Including this value allows a potentially malicious miner to withhold the transaction for an extended period, such as in scenarios like the Flashbots mempool for bundling transactions. This delay could persist until the miner can exploit the transaction to trigger the maximum allowable slippage as per the slippage parameter or until circumstances turn unfavorable enough for the activation of other orders, such as liquidations.
This value allows a potentially malicious miner to withhold the transaction for an extended period
Manual Review
To mitigate this risk, timestamps should be chosen off-chain.
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.