_newFeeIncreasePercentage
.Description: According to the README.md: "It creates a competitive environment where players vie for the title of "King" by paying an increasing fee
. Thus implying that every fee paid by players should be greater than the previous payment. Currently, the _newFeeIncreasePercentage
parameter can be set to 0.
Risk Level:
Impact: Low
While no funds are at risk, it does contradict the intended functionality of the protocol.
Likelihood: Low
This would only occur if the deployer decided to set _newFeeIncreasePercentage
to zero.
Proof of Concept:
Deployer updates the fee to zero
Player 1 claims the throne
Player 2 claims the throne
Compare the fees by both players - (they are the same)
Proof of Code:
Insert this into Game.t.sol
:
Recommended Mitigation: A solution here would be to update the logic in the modifier isValidPercentage
to not allow zero values.
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.