Submission Details
Impact:
Likelihood:
Unused State Variable: `blockTime`
Root + Impact
Description
The contract declares a state variable blockTime, initialized to the current block timestamp, but it is never read or updated anywhere in the codebase.
This indicates dead code and may cause confusion, unnecessary gas costs, and code maintenance issues.
// @> Unused State Variable
uint256 public blockTime = block.timestamp;
Risk: Informational
Likelihood: Low
| Factor | Observation | Likelihood Influence |
|---|---|---|
| Developer Oversight | Variable was likely left from testing or refactoring. | Low |
| Operational Risk | Does not affect runtime logic or user interaction. | Low |
| Maintenance Confusion | Can mislead future developers or auditors. | Medium |
Impact: Low
| Category | Impact Description |
|---|---|
| Gas Efficiency | Adds an unnecessary storage slot, increasing contract deployment cost. |
| Code Clarity | Misleads developers into thinking it is used for time-tracking logic |
| Auditability | Creates noise during security reviews, reducing code readability. |
Proof of Concept
Recommended Mitigation
No security impact, but adds unnecessary gas cost and reduces code quality, it is better to be removed.
- uint256 public blockTime = block.timestamp;
Rewards breakdown
nSLOC
157This 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.