Normal behavior: Events should be emitted with arguments in the same order and semantic meaning as declared so off-chain indexers and tooling parse logs correctly.
Problem: The declared TokensWithdrawn(address indexed token, address indexed to, uint256 amount) event is emitted with arguments in the wrong order, swapping token and to.
Likelihood:
Withdrawal function is callable by owner and will emit this incorrect event on every withdraw call.
Any off-chain consumer (indexer, analytics, explorers) that assumes the declared order will consistently misinterpret logs.
Impact:
No on-chain funds or contract state are altered incorrectly by the emit itself.
Off-chain monitoring, accounting, and forensic tools will show swapped fields, potentially causing misreporting or investigations.
The event arguments are emitted in the wrong order
Change the order of even arguments.
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.