Expected behavior:
Ensure subtraction checks properly.
Actual behavior:
When by > dailyClaimLimit, it reverts but without descriptive reason.
Although the function includes a check (if (by > dailyClaimLimit)), the revert uses a custom error (RaiseBoxFaucet_CurrentClaimLimitIsLessThanBy()), which provides no descriptive reason string. This isn't a functional vulnerability (i.e. no actual underflow or loss of funds), but it poses a risk to usability, debugging, and transparency, particularly in production or when interacting with the contract via low-level tools or UIs.
Likelihood:
adjustDailyClaimLimit()
If this function is onlyOwner, then the risk of abuse is very low — it's under the control of a trusted party.
Impact:
No actual underflow, but poor UX and clarity.
the function reverts when callers attempt to subtract more than the current dailyClaimLimit, and the revert provides a custom error (which is fine technically) but may be considered poor UX
Include reason string or event for transparency.
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.