TokensWithdrawn event is declared as (token, to, amount) but the function emits the parameters in a different order. This causes event logs to map indexed parameters incorrectly, misleading all off-chain systems that rely on topic order for tracking withdrawals. The impact is significant because event data is immutable and heavily relied upon for monitoring and accounting.Describe the normal behavior in one or more sentences
Explain the specific issue or problem in one or more sentences
Likelihood:
Very likely to occur because the incorrect order is hard-coded, meaning every emission produces corrupted logs.
Impact:
Event listeners will misidentify the token address and recipient address, breaking indexing pipelines, dashboards, analytics, and audit trails.
Data consumers may assume withdrawals occurred to incorrect addresses or involving incorrect tokens.
In the test output we can clearly see that the order of the emittion of the event is wrong in context of the event declaration,
Either change the parameter while event declaration or change the parameters while emittion of event.
I am changing the event emission in the TokensWithdrawn function
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.