Submission Details
Severity:
Hardcoded Timestamps
Summary
While hardcoded timestamps reduce flexibility and can lead to potential issues if the deployment doesn't match the expected timeline, they don't pose a direct security risk. It's more about usability and maintainability.
Vulnerability Details
uint256 public constant SELECTION_START_TIME = 1728691200;
uint256 public constant SELECTION_ENDING_TIME = 1728777600;
if (block.timestamp < SELECTION_START_TIME) {
revert ChoosingRam__TimeToBeLikeRamIsNotFinish();
}
if (block.timestamp > SELECTION_ENDING_TIME) {
revert ChoosingRam__EventIsFinished();
}
Impact
This can make the contract less flexible and prone to errors if the deployment time doesn't match the expected time.
Tools Used
Manual review
Recommendations
Consider using a more flexible system for managing event timelines, possibly with initialization parameters.
Updates
Lead Judging Commences
bube about 1 year ago
Submission Judgement Published Reason: Non-acceptable severity
Assigned finding tags:
Info/Gas/Invalid according to docs
Rewards breakdown
nSLOC
218This contest has a flat reward structure with the following payouts:
100 EXP
20 EXP
2 EXP
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.