festivalContract defaults to address(0) with no guard checking for this explicitly. The check conflates "wrong caller" with "contract not configured".
Both functions check:
When festivalContract is address(0) (its default value before setFestivalContract is called), this check passes only if msg.sender == address(0) — impossible for any real caller. The error "Only_Festival_Mint" implies an authorisation failure, but the real cause is a missing deployment step. This delays debugging during integration or staging and can cause the entire reward system to silently fail if setFestivalContract is accidentally skipped.
Likelihood:
Likelihood: Low — deployment sequencing error
Impact:
Impact: Low — no exploit path; deployment misconfiguration causes silent failure with confusing error message
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.