Summary\
This static state deadline variable causes all swaps to rely on a fixed timestamp, risking transaction failure once outdated.
Vulnerability Details\
The deadline
is stored as a state variable and not recalculated per swap.
If not updated via setDeadline
, all subsequent swaps unconditionally use a past timestamp, reverting even for valid transactions.
Swap deadlines must always be in the future relative to execution time (block.timestamp
).
A static deadline
breaks this invariant once block.timestamp
exceeds it, rendering all swaps invalid.
A static deadline
breaks this invariant once block.timestamp
exceeds it, rendering all swaps invalid.
Manual Review
Replace static deadline
with dynamic calculation per swap. Remove the deadline
state variable and associated setDeadline
function to enforce real-time validity for all swap
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.