getOrderDetailsString()
at function inside OrderBook.sol
has redundant logic for computing the status
string.Describe the normal behavior in one or more sentences: The normal behavior is to assign a status regarding if the order is active and the deadline is met.
The initial ternary assignment is completely overwritten which is pointless
Likelihood:
This code runs every time a user calls getOrderDetailsString()
The ternary condition is misleading and unused — could confuse developers or auditors.
Impact:
Gas inefficiency
Confusing or inaccurate order status display
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
View preliminary resultsAppeals are being carefully reviewed by our judges.
The contest is complete and the rewards are being distributed.