A simple typographical error in the field name dealine_set
results in confusion and potential future misuses. While not an immediate exploit itself, it indicates poor code clarity.
The field is spelled dealine_set
throughout, but the intended meaning is deadline_set
.
Maintainers or new developers may misunderstand or incorrectly reference that field.
Higher Likelihood of Mistakes: Future modifications or audits might overlook references to deadline_set
because of the typo.
Code Quality: Reduces confidence in the code’s correctness and thoroughness.
Manual review of the source code.
Comparing field names with expected terminology in the documentation.
Rename the field to deadline_set for more clarity.
Refactor the migration (if necessary) and update the documentation.
This is strong informational finding, there is no impact for the protocol. The variable is the same on all places.
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.