Faulty event emisssion in claim function causing wrong information being logged
The 'claim' function is used by the recipient to claim their reward using the zk proof and the treasure hash
At the end of the function however the event is emitted with wrong information.
Likelihood:
The payment goes out to the 'recipient' but it will be shown as going to msg.sender by off-chain indexers and explorers.
Impact:
The wrong address will be displayed as the beneficiary when the event logs out
Anyone can submit valid ZK proofs on behalf of different callers and misdirect who "appeared" to have found the treasure in the event logs.
Misleading leaderboards or statistics
This PoC test shows a test that shows how one participant calling the 'claim' function can lead to misleading data being logged due to the bug in the event emission code.
The mitigation is not complicated just correct the address logged off in the event to the correct one that is the 'recipient' not 'msg.sender'
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.
The contest is complete and the rewards are being distributed.