The TokensWithdrawn event is meant to accurately log withdrawals by emitting the parameters in the order defined in the event signature.
However, the contract emits the parameters in the wrong order, swapping token and to.
This results in off-chain indexers, analytics, and monitoring systems receiving incorrect withdrawal data.
Likelihood:
Triggered every time the owner withdraws tokens.
Off-chain systems will always process incorrect event data.
Any subgraph or monitoring tool relying on this event will misinterpret withdrawals.
Impact:
Wallets/addresses appear reversed in logs.
Token accounting becomes unreliable or misleading.
Protocol transparency is degraded.
Auditors and integrators may misread treasury movements.
This demonstrates that log consumers will treat the receiver as the token address and the token address as the receiver.
Reorder the event parameters to match the event declaration.
This ensures event data aligns with expectations and off-chain systems process accurate information.
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.