The normal behavior is that Claimed(treasureHash, recipient) reflects the address that receives payout.
The issue is that event emission uses msg.sender instead of the recipient parameter. Off-chain consumers indexing rewards from logs get systematically incorrect attribution.
Likelihood:
Every successful claim emits the wrong second indexed parameter.
Existing test demonstrates this behavior deterministically.
Impact:
Analytics, scoreboards, and monitoring systems receive corrupted claim attribution.
Operational and dispute-resolution workflows relying on event logs can fail.
Standalone reproduction:
Pick msg.sender = participant and recipient = anotherAddress.
Submit a valid claim(proof, treasureHash, recipient).
Inspect emitted log.
Observe second indexed argument equals participant instead of recipient.
Written explanation: the reward can be sent to recipient, but indexers reading the event will record PARTICIPANT as recipient because the contract emits the caller.
Use the function claim(bytes calldata proof, bytes32 treasureHash, address payable recipient).
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.