The contract validates that the participation fee is below PARTICIPATIONFEEBSPMAX (300 basis points) in the constructor, but doesn't check if it's zero, which could lead to unexpected behavior.
Likelihood:
Contract deployment always accepts zero value for participationFeeBsp
This passes current validation since it checks only for exceeding maximum
Impact:
Zero participation fee means no revenue generation for fee recipient
Economic model disruption if fees are part of intended incentive design
Deploy contract with participationFeeBsp = 0, allowing users to participate without paying any fees while still satisfying validation checks.
Add explicit check in constructor to revert if participationFeeBsp == 0, ensuring a meaningful fee is always set.
This is owner action and the owner is assumed to be trusted and to provide correct input arguments.
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.