In function adjustDailyClaimLimit no event is emitted when the claim limit is updated.
This results in a lack of transparency, as off-chain systems such as explorers, dApps, and monitoring tools cannot detect when the daily claim limit is changed. Additionally, this makes auditing more difficult, as there is no on-chain record of previous values or when changes occurred.
Without an emitted event, changes to critical contract parameters happen silently. This:
Prevents off-chain tools from tracking state changes
Makes it harder for users, maintainers, and auditors to reconstruct historical state
May lead to confusion or misinterpretation of claim limit behavior
Likelihood:
Medium
Only callable by onlyOwner, but it can occur every time the function is used. If the owner is governed by DAO or multisig, the lack of an audit trail increases risk
Impact:
Poor transparency
Missing historical data
Reduces trust in the contract’s operation
Weakens incident response and debugging
Emit an event each time the claim limit is changed:
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.