festivalContract
in BeatToken.sol can only be set once within the contract . In future , when there is something like ..lets say an upgrade or a someone makes a mistake when deploying the contract to a blockchain , the contract becomes obsolete and will not be able to be used.
Risk
Likelihood:
The likelihood is medium because it is a config function that's only called once by the owner of the contract
When the address needs to be changed in future it cant be undone and this can cause quite a problem
Impact:
The impact is high because ,since festivalContract
can only be set once in BeatToken.sol , if it is misconfigured in any way , then no one can/will be able to mint and/or burn the tokens anymore
Since no tokens will be minted anymore ,this will hinder the main /core function of the token , most importantly if the main token function is tied to very important activities in the festival such as redeeming tickets
This is intended. It's done like that because the festival contract requires beat token's address and vice versa.
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.