RAACMinter includes functions to modify RAACToken parameters like fee collector and tax rates. These functions require owner privileges on RAACToken which RAACMinter does not have, making these functions unusable. Additionally, even if ownership is transferred to RAACMinter, it lacks functions to call all RAACToken owner privileged functions.
RAACMinter includes the following functions that attempt to call privileged functions on RAACToken:
However, these functions in RAACToken are protected by onlyOwner:
Since RAACMinter is not the owner of RAACToken, these functions will always revert. Additionally, even if ownership is transferred to RAACMinter, it lacks functions to call owner privileged functions like manageWhitelist(), making some RAACToken functionality inaccessible.
Functions in RAACMinter that modify RAACToken parameters are unusable
If ownership is transferred to RAACMinter, some RAACToken owner functions become inaccessible
Unnecessary code that could confuse integrators
No security risk as control remains with RAACToken owner
Tools Used:
Manual Review
Remove these functions from RAACMinter since they cannot work without ownership
If these functions are needed in RAACMinter:
Clearly document that RAACToken ownership must be transferred
Add all necessary functions to access RAACToken owner functionality
Consider redesigning the access control system if RAACMinter genuinely needs these capabilities
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.