Every function on this contract has its own event to help off-chain data fetching
This functions doesn't have its own event
Likelihood:
Reason 1: This will occur every time a user interacts with the affected function, since no event is emitted to log the action on-chain.
Reason 2: Off-chain applications relying on logs for state synchronization (such as UIs or The Graph subgraphs) will not detect these state changes automatically.
Impact:
Impact 1: The impact on protocol logic is very low, as the absence of an event does not affect the correctness of on-chain operations.
Impact 2: However, it can make integration with front-end or off-chain services more complex, as they would need to perform manual state reads instead of listening for emitted logs.
Emit a dedicated event (e.g., TokenBurn(uint256 amount, uint timestamp) ).
This improves transparency, eases integration with monitoring tools, and simplifies debugging or auditability.
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.