dailySepEthCap value in deploy and test scripts, can lead to wrong test conclusionsExpected bahaviour The value of dailySepEthCap is set upon deployment. The README does not detail which cap will be used. The deploy script and the test scripts should use consistent cap values, given that the value never changes after the contract is deployed.
Problematic bahaviour The deploy script uses 1 ether as the dailySepEthCap, while the test script 0.5 ether. If the 0.5 ether value is the correct one, the deploy script should be adjusted.
Root cause:
Likelihood: Low
Given that the dailySepEthCap threshold is set upon deployment, an incorrect assignment will affect all incoming transactions. However, this incosistency will be reviewed before deployment, reducing its likelihood.
Impact: Low
An incorrect threshold assignment will impact the number of first-time user claims that can be processed by the faucet.
If 0.5 ether is the intended cap value, assigning it to 1 ether will allow double the amount of eth claims, draining the eth balance of the contract much faster.
A PoC is not necessary.
If 0.5 ether is the intended dailySepEthCap value, change the deploy script to:
Enhance the contract's documentation accordingly so that the intend is clear.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
View preliminary resultsAppeals are being carefully reviewed by our judges.
The contest is complete and the rewards are being distributed.