The faucet is designed to allow 1000 token claims per day to support adequate testing activity for the testnet protocol. This daily limit controls how many users can claim faucet tokens within a 24-hour period and is a critical parameter for the faucet's operational capacity.
The dailyClaimLimit is incorrectly initialized to 100 instead of 1000, artificially restricting the number of daily claims to 10% of the intended capacity. This severely limits the faucet's utility for testnet operations and contradicts the protocol's stated requirements in the contract documentation.
Likelihood:
The contract will deploy with this incorrect value and immediately begin enforcing the wrong limit from day one
Every single day of operation will be affected by this misconfiguration until manually adjusted by the owner
The issue exists in the initial state variable declaration, making it unavoidable without code changes
Impact:
Only 100 users can claim tokens daily instead of the intended 1000, reducing testnet participation by 90%
Legitimate users will be blocked from claiming tokens after the 100th claim of the day, causing user frustration
The testnet protocol that depends on these tokens will have insufficient users for proper testing and quality assurance
The owner must manually call adjustDailyClaimLimit() after deployment to fix this, incurring additional gas costs
This reduces the faucet's effectiveness for its primary purpose: distributing test tokens to enable protocol testing
This scenario demonstrates how the incorrect limit blocks legitimate users:
Change the initial value of dailyClaimLimit from 100 to 1000 to match the protocol specification. This ensures the faucet operates at the intended capacity from deployment without requiring manual intervention.
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.