The claim() function is intended to mark a treasure as claimed after a valid proof is submitted, preventing the same proof from being used again. The replay guard checks claimed[_treasureHash], where _treasureHash is a private immutable that is never assigned and defaults to bytes32(0). However, the claim is recorded using the function parameter claimed[treasureHash]. Since these keys differ, the check and the write operate on different storage slots, causing the replay protection to never trigger.
Likelihood:
Any participant who finds a treasure has a valid proof with their address as recipient
Replaying requires no additional capital — same calldata submitted multiple times
No special access or timing required — works any time the contract is unpaused and funded
Impact:
Full contract drain of up to MAX_TREASURES × REWARD using a single valid proof
claimsCount hits MAX_TREASURES via replay, permanently locking out all legitimate finders with AllTreasuresClaimed
Contract state corrupted — remaining treasure hashes appear unclaimed via isClaimed() but can never be claimed
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.