The _deployTimestamp
was not initialized; leaving it to be malleable.
The _deployTimestamp
is in the constructor.
It can cause havoc where it is used to calculate timing in the contract because it was not initialized to a value.
Timing precision loss.
Manual review.
Set the _deployTimestamp
to 0 first before assigning it directly to block.timestamp
.
This way, it will be initialized to a value, and the timing calculation hereafter will be precise.
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.