The Pot
contract constructor accepts arrays of players
and rewards
to initialize the contract. However, there is no validation to ensure that these arrays are non-empty. This lack of validation can lead to the creation of a contract with an inconsistent state, where no players or rewards exist, potentially causing failures in subsequent operations.
The constructor accepts two arrays, players
and rewards
, but does not verify whether these arrays are empty.
Functions that rely on the existence of players or rewards, such as reward claims or distribution, will fail or produce incorrect results if the arrays are empty.
Manual Review
Add checks in the constructor to ensure that both the players
and rewards
arrays are non-empty.
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.